Getting system error messages
This month we will cover a rather esoteric intrinsic for most COBOL developers, and that is the GENMESSAGE intrinsic. Essentially this allows you to retrieve the actual message from the system catalog for the error that is returned from various commands.
I use this technique in several programs that I wrote. One of them is in an MPEX-ish type program I wrote (because I couldnt afford to buy MPEX for my personal use) and I needed to handle MPE commands in it, so if there was something wrong with the command I wanted to display the actual system error message.
The other scenario I use it for is in a client-server program I wrote. The server sometimes issues MPE commands that are initiated by the client. The server doesnt really care what the result is, but the client does, so I get the message back from the system catalog and pass it back to the client and throw it up in a message box. This works out pretty darn well, actually.
So by now you are all
excited, sitting by your keyboard ready to start typing. Wait no
more, the figure below shows the code.
01 USER-COMMAND PIC X(78) VALUE SPACES. 01 CAT-FILE PIC X(28) VALUE "CATALOG.PUB.SYS". 01 CAT-FNUM PIC S9(4) COMP VALUE 0. 01 CAT-ERR PIC S9(4) COMP VALUE 0. 01 CAT-BUFF PIC X(78) VALUE SPACES. * 01 COM-IMAGE. 05 COMMAND-IMAGE PIC X(79) VALUE SPACES. 05 PIC X VALUE %15. 01 COMMAND-ERROR PIC S9(4) COMP VALUE 0. 01 ERR-PARM PIC S9(4) COMP VALUE 0. PROCEDURE DIVISION. A0000-MACROS. $DEFINE %COMIMAGE= MOVE !1 TO COMMAND-IMAGE CALL INTRINSIC 'COMMAND' USING COM-IMAGE, COMMAND-ERROR, ERR-PARM IF COMMAND-ERROR <> 0 MOVE SPACES TO CAT-BUFF CALL INTRINSIC "GENMESSAGE" USING CAT-FNUM, 2, COMMAND-ERROR, CAT-BUFF, 78, \\, \\, \\, \\, \\, \\, \\, CAT-ERR DISPLAY CAT-BUFF END-IF IF ERR-PARM > 1 MOVE SPACES TO CAT-BUFF CALL INTRINSIC "GENMESSAGE" USING CAT-FNUM, 8, ERR-PARM, CAT-BUFF, 78, \\, \\, \\, \\, \\, \\, \\, CAT-ERR DISPLAY CAT-BUFF END-IF# A1000-INIT. CALL INTRINSIC "FOPEN" USING CAT-FILE, %5, %2720 GIVING CAT-FNUM. ACCEPT USER-COMMAND FREE. %COMIMAGE(USER-COMMAND#).
So the first thing we have to do is FOPEN the system catalog file CATALOG.PUB.SYS. For those of you who like to know, the %5 for foptions is a binary 101, which means open the file as an old permanent ASCII file. The %2720 for aoptions is a binary 10111010000 which means the file is read only, multi-record, no FLOCK, shared non-buffered access, that allows inter-job multi-access.
As usual I am using a MACRO to make use of the COMMAND intrinsic, and do a check of any errors that might be returned. If there is an error, then we call GENMESSAGE to get the text of the error number. First if the variable COMMAND-ERROR is not equal to zero, then that indicates a CIERROR has occurred. We then call GENMESSAGE passing the FNUM that we retrieved in the FOPEN of the catalog file. The message set is 2 to specify that we want the CI message set out of the catalog (there are messages for all sorts of subsystems in the catalog).
Then we pass the error number that was returned from the command intrinsic, a buffer to hold the message, and the length of the buffer. Finally there is a variable to hold any error that occurs in the call to GENMESSAGE. I am being lazy here, and I am not checking the return error value.
The last step of course is to display CAT-BUFF to see what the message was. Now you are probably wondering why I call GENMESSAGE again. Well if the value in ERR-PARM is greater than 1, then that means we also got a file system error, and we are going to want to know what it is. So now we call GENMESSAGE with a message set of 8, and with ERR-PARM so we can get the file system error message. Finally, we display CAT-BUFF again to see what the error was.
Its not hard to do, but you do need to know the steps involved. As I said, there are lots of message sets in the system catalog. The only ones here that we are dealing with are 2 and 8, so there are other options that you can come up with.
Dont forget to send
your tips in, I get lonely sometimes.
Shawn Gordon, whose S.M. Gordon & Associates firm supplies HP 3000 utilities, has worked with 3000s since 1983.
Copyright The 3000 NewsWire. All rights reserved.