You receive COBOL error messages that start with IGY. However, you are unable to find a manual where the messages are documented.
As documented in About this information of the Enterprise COBOL for z/OS 6.2 documentation under Messages and Codes, some of the COBOL compiler error messages are not documented in any manual because the messages are considered to be self explanatory.
Resolving The Problem
The Messages and codes topic was added to the Enterprise COBOL for z/OS V6.2.0 documentation in 2017. However, not all messages are included in the topic because many are considered to be self explanatory.
The messages that are included in the documentation have also been added to the IBM Doc Buddy mobile app. Note that you will not have to download the latest app version to receive message updates.
You can get a list of all COBOL messages ass documented in topic Generating a list of compiler messages in the Enterprise COBOL for z/OS V6.2 Programming Guide:
You can generate a complete listing of compiler diagnostic messages with their message numbers, severities, and text by compiling a program that has program-name ERRMSG.
You can code just the PROGRAM-ID paragraph, as shown below, and omit the rest of the program.
The above is true with all releases of COBOL. The compile listing includes an explanation of the format of the messages generated during compilation and the severity levels of the messages. It also includes a list of the actual messages, but no further explanation of the messages.
For COBOL documentation, you can send feedback directly to firstname.lastname@example.org as documented in topic How to send your comments. You are encouraged to do this if you do NOT think a message is self explanatory and you would like to request that IBM include the message in the Messages and codes topic in the documentation with an explanation, system action, and user response.
Internal Use Only
Jia Lei Ma/China/IBM (Doc Buddy Team) "We update the messages per requests from the ID teams and will push the updates to users when available. Users don't have to download the latest app version to receive the message updates. "
Blog where I found out about NEW COBOL message manual:
|ID Transformation Newsletter 2017 3Q - Project Highlights blog entry in the Global IBM Z Community blog.|
Changed from this on 10/31/17:
Unfortunately, there is no further detail for the individual COBOL messages other than what you see in the messages. This is because the messages are thought to be self explanatory. If you do not think a message is self explanatory, please visit the Servers and Systems Software RFE Community and open a COBOL Request For Enhancement (RFE). Specify the messages that you think need further explanation and why.
Removed message file based on this - 4/12/2016 (also submitted managenow ticket to have message file removed from the Google index)
This is not working the way that I expected it to work. It was always my understanding and experience that if I included an attachment in certain formats like a PDF or a .txt file that it would be indexed by Google. This is also what we have documented under Attachment in the Support Content information wiki as follows:
To make the content of the file available during a search, make sure the file format is a text (Wordpad or Notepad), PDF, html, xml, zip, or gzip file. Other file types, such as presentation formats, are not made searchable. PDFs and text files are indexed for searching. DCF indexing of the files will not occur until the item is published.
But, to see the technote in the search results I had to ncluded "message" in my search terms. Here you can see it returned:
Since it's unlikely that someone would be searching on the message and the words "cobol message", I can go ahead and publish the technote without the attachment but am also going to have to request that the file be removed from the web if it bothers you that the out-dated file is on the web. Let me know if you think it's worth the time.
Create new COBOL listing using MVS24:
USASSC4.CICSR620.JCL(COBMSGS) - the program
BATCHCO2 --------- STRING(S) FOUND -------------------
12 //COB.SYSIN DD DSN=USASSC4.CICSR620.JCL(COBMSGS),DISP=SHR
15 NAME COBMSGS(R)
proc uses AD370HLQ='PP.COBOL390.V120', - updated to 3.3.1 libs ub May 2005
Tony Hogg got me the 3.3.1 libraries on MVS24.Sent note to Tony asking him if 3.3 libraries are available. This is what I found on MVS24...
Paul didn't know of any 3.3 libraries.
** Updated proc again on 19 June 2008 with the following:
// AD370HLQ='PP.COBOL390.V340', Updated 6-19-08
// LE370HLQ='PP.ADLE370.ZOS190', Updated 6-19-08
- also, copied JCL from USASSC4.CICSR620.JCL TO USASSC4.CICS.JCL so that it won't get lost when the 620 libraries are deleted.
To copy messages from the output queue to a file on your pc:
PRINT output from S.DA (USE PRINT AT TOP OF SCREEN):
2. PRINT ODSN dataset-name (without the hlq usasscx)
- open dataset (to create and open print dataset) -NEW FB 133
- you can specify SHR if the dataset is already created
4. PRINT Lines (write to print dataset, leave black to capture all line
5. PRINT Close (to close and make available)
enter "=x' to go back to the TSO ready prompt, note the session letter
bring up a windows command prompt (enter "cmd" in Run)
enter "cd \" to get back to "c:\>" directory (home)
enter "cd temp" to get to temp directory (directory to write to)
enter "receive cobol.messages c: 'USASSC4.COBOL.MESSAGES' ASCII CRL
where cobol.messages is the name of the file on the PC to create and w
where e: is the session that your TSO ready prompt is sitting on
where USASSC4.COBOL.MESSAGE.LIST is the name of the file on TSO
where ASCII and CRLF is used to bring the file down as a text file.
You can generate a list of compiler error messages as documented in the COBOL for z/OS® and OS/390® Programming Guide Version 3 Release 3:
You can generate a complete listing of compiler diagnostic messages, with their explanations, by compiling a program with a program name of ERRMSG specified in the PROGRAM-ID paragraph, like this:
You can omit the rest of the program.
COBOL2 COBOL/2 COBOLII COBOL/370 messages IGY 5697E9300 R200 200 R620 620 R630 630 HCI6300 HCI6200 5697-E93 5697E93 5655M1500 R640 640 R400 400 HCI6400 R650 650 R500 500 HCI6500 5655-M15 5655M15 KIXINFO
CICS 3.1 manuals:
OS/VS COBOL programs must be upgraded to Language Environment conforming COBOL, and recompiled against a level of COBOL compiler supported by CICS. The CICS Release
Guide lists the compilers supported by CICS. Enterprise COBOL for z/OS and OS/390 is the recommended compiler.
Following is an attachment containing the compile output from compiling the above program with IBM Enterprise COBOL for z/OS V3.4:
Following is an attachment containing the compile output from compiling the above program with IBM Enterprise COBOL for z/OS and OS/390 V3.3.1:
Following is an OLD attachment containing the compile output from compiling the above program with IBM Enterprise COBOL for z/OS and OS/390 3.1.0:
CICS/TS CICS TS CICS Transaction Server
15 June 2018