HP3000-L Archives

January 2010, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Roy Brown <[log in to unmask]>
Reply To:
Roy Brown <[log in to unmask]>
Date:
Mon, 25 Jan 2010 01:20:16 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (84 lines)
In message <[log in to unmask]>, Brian 
Donaldson <[log in to unmask]> writing at 00:11:43 in his/her local time 
opines:-
>I had added the XEQERR portion AFTER the command intrinsic returned error
>code=0 and param=0 when actually the call had failed with the error:
>
>INVALID RESULTANT BLOCK SIZE  (FSERR 11)
>
>It was then that I added the logic to send the output to the file XEQERR
>which I don't really need in the long run anyway. I'll probably take all
>that back out once I figure out how to get around the problem.
>
>Strangely enough, I got it to work by changing the CM KSAM file from a
>BINARY file to an ASCII file thus:
>
>KSAMCMF1.PUB.DEV & KSAMCMK1 ARE CREATED.
>
>
>However, that still doesn't solve the problem with the COMMAND intrinsic.
>
>Here's the code snippet :
>
> 01  WS-ERROR-CODE               PIC S9(04) COMP VALUE ZEROES.
> 01  WS-PARAM                         PIC S9(04) COMP VALUE ZEROES.
>
> 01  WS-COMMAND-LINE.
>     05  WS-CL-BUFFER      PIC X(499)      VALUE SPACES.
>     05  WS-CL-CR              PIC X(001)      VALUE %15.
>
> 01  WS-KSAMUTIL-BUILD-LINE.
>     05  FILLER                       PIC  X(40)  VALUE
>     'RUN KSAMUTIL.PUB.SYS < XEQFILE > *XEQERR'.
>
>PROCEDURE DIVISION.
>
>
>
>....
>...
>
>     MOVE SPACES                 TO WS-CL-BUFFER
>     MOVE WS-KSAMUTIL-BUILD-LINE TO WS-CL-BUFFER
>     MOVE %15                    TO WS-CL-CR
>
>     MOVE ZEROES                 TO WS-ERROR-CODE
>     MOVE ZEROES                 TO WS-MSGNUM
>     MOVE ZEROES                 TO WS-PARAM
>     MOVE ZEROES                 TO ERR-FLAG
>
>     CALL INTRINSIC "COMMAND" USING WS-COMMAND-LINE
>                                    WS-ERROR-CODE
>                                    WS-PARAM
>
>     DISPLAY ">" WS-ERROR-CODE ">" WS-PARAM ">" WS-CL-BUFFER "<"
>
>     IF WS-ERROR-CODE <> ZEROES THEN
>        MOVE 631 TO WS-MSGNUM
>        MOVE 1   TO ERR-FLAG
>        GO TO A105-EXIT
>     END-IF
>
>     IF WS-PARAM <> ZEROES THEN
>        MOVE 632      TO WS-MSGNUM
>        MOVE WS-PARAM TO WS-ERROR-CODE
>        MOVE ZEROES   TO WS-PARAM
>        MOVE 1        TO ERR-FLAG
>        GO TO A105-EXIT
>     END-IF

Hmmm.

Try 'RUN NONEXIST' as your WS-CL-BUFFER.

Assuming you don't have a program called NONEXIST, that should provoke a 
CI error, as distinct from a program that is successfully launched, but 
gives a *program* error. Assuming such a distinction exists, of course.

-- 
Roy Brown        'Have nothing in your houses that you do not know to be
Kelmscott Ltd     useful, or believe to be beautiful'  William Morris

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2