Dave This response is also taking into account other responses in this thread.
I'm glad you are now working mainly with help from John McKown. I have just dealt with a very similar message-based issue, specifically relating to Language Environment codes, with a customer and also in the ibmtcp-l list. Let us review how you could have been more self-sufficient. The starting point is what the system gave you: message CEE5101C. As Peter Hunkeler pointed out, even if you know all of the component- identifying letters, the easiest way to find your way to an explanation is the IBM LookAt! web page. Thus, for CEE5101C, we find: <quote> 1.513 CEE5101C CEE5101C During initialization, the callable service BPX1MSS failed. The system return code was return_code; the reason code was reason_code. The application will be terminated. Explanation: The callable service BPX1MSS failed with return code return_code and reason code reason_code because the application was not authorized to use UNIX System Services. Programmer Response: Contact your system administrator to have the id registered with UNIX System Services to use these services. See z/OS UNIX System Services Programming: Assembler Callable Services Reference for the appropriate action to take for this return code and reason code. Consult with your UNIX System Services support personnel if necessary. System Action: The application is terminated. Symbolic Feedback Code: CEE4VD </quote> So I'd be inclined to say that the "key" was just finding the explanation of the message in the manual. John McKown offered a short-cut based on having spotted an 8-character hexadecimal string in the message text. No doubt in his sleep he can now perform the trick of using BPXMTEXT in order to translate such a string into what the developer at least considers is English. The labour-intensive alternative to using BPXMTEXT for the "reason code" text is simply to follow-up what the online version of the message offers and follow the link to the suggested manual. I have to admit that there is a bit of stupidity here requiring a bit of confidence in following links. The manual to which you are directed is z/OS UNIX System Services Programming: Assembler Callable Services Reference. This does not look quite so helpful at first glance. What you need to do is pluck up some courage and look for likely headings in the Contents. It is to be hoped that your eye quickly spots "Return_Code" and "Reason_Code". The nonsense is that you find yourself directed to yet another manual where the golden keys are to be found: z/OS UNIX System Services Messages and Codes in both cases, wouldn't you know? You are now allowed, soto voce of course, to express your disgust at having so pointlessly to look up, albeit with the click of a mouse, two manuals when one would have sufficed. The golden keys are: "return code was 0000000156" >From "3.0 Return Codes (Errnos) Listed by Value" Decimal Value: 156 Hexadecimal Value: 9C Return Code: EMVSINITIAL Description: Process Initialization error. and "reason code was 0B0C00FA" >From "4.2 Reason Codes" Value: 00FA Description: JRSAFGroupNoOMVS The current group does not have a GID defined in the OMVS segment. Action: Create an OMVS segment with a GID. QED! Chris Mason ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html