Language processor return codes

x’04-000’

End of file on file name.

x’08-xxx’

DDNAME not found. Check spelling of ddname.

x’0C-xxx’

FREEMAIN error. Contact BMC Support.

x’10-000’

File already closed, can’t close it again. Contact BMC Support.

x’1C-000’

File already opened, can’t open it again. Contact BMC Support.

x’20-000’

Skeleton FCB class not found. Contact BMC Support.

x’2C-000’

Function code passed is not valid. Contact BMC Support.

x’30-xxx’

GETMAIN error. Contact BMC Support.

x’34-000’

DCB DCBOFLGS, bit DCBOFOPN is not set after open. Contact BMC Support.

x’38-xxx’

Bad note. Contact BMC Support.

x’3C-xxx’

Bad pointer for point. Contact BMC Support.

x’40-xxx’

Bad write.

x’40-030’

•Member is in use by another job or task.

x’40-044’

•File is out of EXTENTS. Delete unused members or allocate a new file and format it.

•Member is out of EXTENTS. Allocate a new file and format it with a larger group count.

•No more directory space available. Allocate a new file and format it with more directory space or delete unused members.

x’40-xxx’ Contact BMC Support.

x’44-xxx’

Bad read. Contact BMC Support.

x’48-xxx’

Bad Open Member. Contact BMC Support.

x’48-004’, x’48-018’, x’48-068’

•File not formatted. Format file using CWDDSUTL or CWDDALLU.

•File may be corrupted. Contact BMC Support.

x’48-02C’

•Member not found. Possible cause: Invalid PROGRAM-ID. The program name must not be a reserved word or contain invalid characters. Contact BMC Support.

x’48-030’

•Member is in use by another job or task.

x’48-044’

•File is out of EXTENTS. Delete unused members or allocate a new file and format it.

•Member is out of EXTENTS. Allocate a new file and format it with a larger block size.

•No more directory space available. Allocate a new file and format it with more directory space, or delete unused members.

x’48-046’

•Shared directory was specified and none of the attached databases were eligible for use, or not enough space was found in the attached databases for the new member. Review attached databases, and either delete unused members, create another database in the shared directory, or set up DYNCREATE dynamic database creation capability.

-x’48-310’

•Shared directory is out of space needed to add new member information. Use the utility function EXPAND (online advanced functions for shared directory, or batch CWDDLPUT) to increase the file size.

x’48-xxx’

• "The 'xxx' code should correspond to the MVS DDIO and Interface Manager Return Codes table. For more information on the return codes, see MVS DDIO and Interface Manager Return Codes.

The 'xxx' is the x'xxxx' (hexidecimal) return code. For more clarification, contact BMC Support.

x’4C-xxx’

Bad Close Member. Contact BMC Support.

Pxmmmm001-S

COBOL option LIST or OFFSET not specified.

Explanation: A Procedure Map (LIST) or a Condensed Listing (OFFSET) required.

Severity: No COBOL verbs are merged into the Procedure Division.

User Response: Specify appropriate compiler option (LIST, LISTX, OFFSET, or CLIST) to generate a Procedure Map or Condensed Listing.

Pxmmmm002-S

COBOL option MAP not specified.

Explanation: A Data Division Map is required.

Severity: The language processor returns RC=8. Processing may continue, but with unpredictable results.

User Response: Specify appropriate compiler option (MAP or DMAP) to generate a Data Division Map.

Pxmmmm003-S

COBOL option XREF not specified.

Explanation: A cross-reference is required.

Severity: The language processor terminates.

User Response: Specify appropriate compiler option (XREF, XREF(xxx), or SXREF) to generate a cross-reference.

Pxmmmm004-S

COBOL option NOWORD not specified.

Explanation: A cross-reference is required.

Severity: The language processor terminates.

User Response: Specify appropriate compiler option (NOWORD) to generate a cross-reference.

Pxmmmm005-S

COBOL listing not complete.

Explanation: Message Pxmmmm001, Pxmmmm003, Pxmmmm007, or Pxmmmm224 was issued, or one or more of the COBOL Divisions could not be found. A previous message will indicate what section is missing.

Severity: The language processor terminates.

User Response: Check for message Pxmmmm001 - Pxmmmm003, Pxmmmm007, Pxmmmm224, or the missing COBOL Division in the listing. Add missing compiler options, if necessary. If neither condition is found, contact BMC Support.

Pxmmmm006-S

xxxxxxxx file xxxxxxxx, xxxxxxxx error, Return Code=nn.

Explanation: One of the following types of errors was issued on the specified file: CLOSE, CLOSEMEM, NOTE, OPEN, OPENMEM, POINT, READ, WRITE. A language processor return code is generated.

Severity: The language processor terminates.

User Response: Correct the JCL and resubmit the job. When you receive a CWPDDIO OPENMEM error, you might need to allocate a new CWPDDIO file.

Pxmmmm007-S

xxxxxxxxxxxxxxxxxxxx not found.

Explanation: A section of the listing was not found. Missing sections could be one of the following: condensed or assembler listing, data division, data name map, memory map, options, procedure division, or cross-reference.

Severity: The language processor terminates.

User Response: Check for messages Pxmmmm001 - Pxmmmm003. If the messages are not present, then check the COBOL listing for the section indicated by this message. If you do not find the section, perform the steps necessary to generate this section. If the section is present, contact BMC Support.

Pxmmmm008-S

Language not determined, processing may not be complete.

Explanation: The version of the compiler cannot be determined from the first header of the listing. This may be due to an error in the CWPPRTI file or because the header record does not match the formats coded. This can also occur if the compiler listing input to the postprocessor is the wrong language (for example, Assembler or PL/I).

Severity: The listing is processed with the language defined.

User Response: Check for correct assignment of the CWPPRTI file. Retain the COBOL listing and contact BMC Support to define the header format and eliminate the error.

Pxmmmm009-S

Bad Return code from sort. RC=nn.

Explanation: The sort was not completed successfully.

Severity: The listing is processed with work records in their current order.

User Response: Check your sort manual for the meaning of the sort return code, and any messages printed by the sort. Follow the instructions indicated by the sort manual.

Pxmmmm010-S

No more available extents on DDIO file.

Explanation: The language processor encountered an out-of-space condition while writing to the DDIO file.

Severity: The listing is processed, but is not written, to the DDIO file.

User Response: Resolve the file full condition or use another DDIO file. To resolve the file full condition, you may delete members from the current DDIO file or rebuild the current file with more capacity.

Pxmmmm011-S

No more directory blocks available on DDIO file.

Explanation: A new member cannot be opened because the maximum REPTCOUNT has been reached and autodelete processing cannot find any members eligible for deletion.

Severity: The listing is processed but is not written to the DDIO file.

User Response: Resolve the file full condition or use another DDIO file. To resolve the file full condition, you may delete members from the current DDIO file or rebuild the current file with a larger REPTCOUNT value.

Pxmmmm012-S

No more extents allowed for member on DDIO file.

Explanation: The DDIO file being written has reached the maximum number of extents allowed for the file.

Severity: The listing is processed, but is not written, to the DDIO file.

User Response: Use another DDIO file that allows more extents or which has a larger GROUPCOUNT/BLKSIZE combination. You may also rebuild this DDIO file to have a larger block size and/or GROUPCOUNT value.

Pxmmmm013-W

Too many ")" found. Skipping to next valid option.

Explanation: While processing the LP parameters, a parenthesis ‘)’ was encountered where none was expected.

Severity: The language processor skips to the next valid option.

User Response: Verify that all parentheses are entered correctly in the LP parameter options and update if necessary.

Pxmmmm014-W

Looking for "(" found "xxxxxxxx". Skipping to next valid option.

Explanation: The language processor options were entered incorrectly.

Severity: The language processor skips to the next valid option.

User Response: Verify that all LP parameters are entered properly, that all parentheses are entered correctly, and update if necessary. Add any missing subparameters. Check for misspelled parameters and keywords.

Pxmmmm015-W

Looking for ")" found "xxxxxxxx". Skipping to next valid option.

Explanation: The language processor options were entered incorrectly.

Severity: The language processor skips to the next valid option.

User Response: Verify that all LP parameters are entered properly, that all parentheses are entered correctly, and update if necessary. Add any missing subparameters. Check for misspelled parameters and keywords.

Pxmmmm016-W

Looking for valid data found "(" or ")". Skipping to next valid option.

Explanation: The language processor options were entered incorrectly. A keyword is missing.

Severity: The language processor skips to the next valid option.

User Response: Verify that all LP parameters are entered properly, that all parentheses are entered correctly, and update if necessary. Add any missing subparameters. Check for misspelled parameters and keywords.

Pxmmmm017-I 

W-level messages will not be merged in source listing.

Explanation: Informational message due to requested option. Either the PROCESSOR(WARNINGS(NONE)) command or the PROCESSOR(WARNINGS(NOEMBED)) command was specified.

Severity: W-level messages will not be merged in the source listing.

User Response: To merge W-level messages into the source listing, specify the COBOL compiler options PROCESSOR(WARNINGS(EMBED)) command or remove any PROCESSOR(WARNINGS(NONE or NOEMBED) commands.

Pxmmmm018-I W

W-level messages will not be printed at the beginning of the source listing.

Explanation: Informational message due to requested option. The PROCESSOR(WARNINGS(NOFRONT)) command was specified.

Severity: W-level messages will not be printed at the beginning of the source listing.

User Response: To print W-level messages at the front of the listing, specify the COBOL compiler option PROCESSOR(WARNINGS(FRONT)) command or the PROCESSOR(WARNINGS(BOTH)) command, or remove the PROCESSOR(WARNINGS(NOFRONT)) command.

Pxmmmm019-I through Pxmmmm023

Pxmmmm024-I

Pxmmmm025-W

Data found xxxxxxxxxx longer than valid, data truncated to xxxxxxxx.

Explanation: A ddname or file name was longer than allowed.

Severity: Data was truncated to maximum allowable length.

User Response: Correct the JCL and resubmit the job.

Pxmmmm026-W

xxxxxxxxxx is not a valid keyword. Skipping to next valid keyword.

Explanation: The language processor options have been entered incorrectly. Keyword specified is not a valid keyword.

Severity: The language processor skips to the next valid keyword.

User Response: Correct the spelling of the keyword or remove it.

Pxmmmm027-I

xxxxxxxx

Explanation: A language processor option was specified.

Severity: A listing of the options selected is printed.

User Response: None required.

Pxmmmm028-I

xxxxxxxx

Explanation: A language processor option was specified.

Severity: A listing of the options selected is printed.

User Response: None required.

Pxmmmm029-W

CSECT name xxxxxxxx not found in the load text dataset.

Explanation: Specified CSECT cannot be found in the load data set. This message may occur if the CWPLOAD dd statement points to a data set that contains an object module that does not match the compiler listing.

Severity: The language processor text is not appended.

User Response: Correct the JCL and resubmit the job. Ensure that your JCL has the correct definition for the object deck (SYSLIN or SYSPUNCH).

Pxmmmm030-W

“END” text not found for CSECT xxxxxxxx in the load text dataset.

Explanation: No END statement was found for specified CSECT. This message may occur if the CWPLOAD dd statement points to a data set that contains an incomplete object module.

Severity: The language processor text is not appended.

User Response: Correct the JCL and resubmit the job. Ensure that your JCL has the correct definition for the object deck (SYSLIN or SYSPUNCH).

Pxmmmm031-W

Processor text already present for CSECT xxxxxxxx in the load text dataset.

Explanation: Specified CSECT has already been processed by the language processor. This message may occur if the CWPLOAD dd statement specifies DISP=MOD.

Severity: Non-executable text code is not added to the CSECT.

User Response: Correct the JCL and resubmit the job. Ensure that your JCL has the correct definition for the object deck (SYSLIN or SYSPUNCH).

Pxmmmm032-W

CSECT name xxxxxxxx not found in the deck text dataset.

Explanation: Specified CSECT cannot be found in the deck data set. This message may occur if the CWPDECK dd statement points to a data set that contains an object module that does not match the compiler listing.

Severity: The language processor text is not appended.

User Response: Correct the JCL and resubmit the job. Ensure that your JCL has the correct definition for the object deck (SYSLIN or SYSPUNCH).

Pxmmmm033-W

“END” text not found for CSECT xxxxxxxx in the deck text dataset.

Explanation: No END statement was found for the specified CSECT. This message may occur if the CWPDECK dd statement points to a data set that contains an incomplete object module.

Severity: The language processor text is not appended.

User Response: Correct the JCL and resubmit the job. Ensure that your JCL has the correct definition for the object deck (SYSLIN or SYSPUNCH).

Pxmmmm034-W

Processor text already present for CSECT xxxxxxxx in the deck text dataset.

Explanation: Specified CSECT has already been processed by the language processor. This message may occur if the CWPDECK dd statement specifies DISP=MOD.

Severity: Non-executable text code is not added to the CSECT.

User Response: Correct the JCL and resubmit the job. Ensure that your JCL has the correct definition for the object deck (SYSLIN or SYSPUNCH).

Pxmmmm035-W

The Condensed Listing or the Assembler Listing was not found.

Explanation: The message is issued in conjunction with messages Pxmmmm001 or Pxmmmm224 if the appropriate options are not specified.

Severity: The language processor terminates.

User Response: Correct the compiler options and resubmit the job.

Pxmmmm036-S

xxxxxxxx file xxxxxxxx must contain either machine or ASA carriage control.

Explanation: The COBOL listing (SYSPRINT), which is input to the language processor, must contain either machine- or ASA-carriage control characters.

Severity: The language processor terminates.

User Response: Ensure that the compiler listing input into the language processor contains either machine- or ASA-carriage control characters.

Pxmmmm037-S

Load module xxxxxxxx not found, RC=nn.

Explanation: The processor could not find a required load module.

Severity: The language processor terminates.

User Response: Ensure that your STEPLIB contains the correct libraries, and if so, contact BMC Support. The return code indicates the missing module. The following are possible return codes: RC=0 - Operating system is invalid. RC=04 - Load Module named is not found. RC=08 - Load Module named is not found. RC=1 - CUST not found. RC=2 - HED1 not found. RC=3 - LTR not found. RC=4 - HED2 not found. RC=10 - CUSTDB, CCATCUS2, CWCUST and CUSTTD not found. RC=21 - DBAAHED1 not found. RC=22 - CCAAHED1 not found. RC=23 - xxxAHED1 not found (xxx = opsys prefix). RC=24 - TDUGHED1 not found. RC=31 - DBAAHED2 not found. RC=32 - CCAAHED2 not found. RC=33 - xxxAHED2 not found (xxx = opsys prefix). RC=34 - TDUGHED2 not found. RC=41 - DBAActl2 not found. RC=42 - CCAActl2 not found. RC=43 - xxxAltr not found (xxx = opsys prefix). RC=44 - TDUGLTRS not found. RC=51 - CUSTDB used for customer error messages. RC=52 - Product timed out. RC=53 - Option timed out. RC=54 - CUSTTD used for customer error messages.

Pxmmmm038-I

No override options found. Default options used.

Explanation: Informational message indicating the options used are the default options shipped or as configured by your site.

Severity: Print the message and continue processing.

User Response: To use different options, add them to the PARM statement on the EXEC card or in the CWPPRMO file.

Pxmmmm039-S

Could not get storage. Bytes requested = nnnnnnnn.

Explanation: An error occurred while obtaining storage. The length indicated in the message is the length of the storage that was requested while obtaining storage.

Severity: The language processor terminates.

User Response: Change the size parameter on the EXEC card, change the region size on the JOB card, or change the buffer size for the work files to obtain the storage needed to process the listing.

Pxmmmm040-W

Data set xxxxxxxx is empty.

Explanation: The data set specified by xxxxxxxx is empty and cannot be used as input to the language processor.

Severity: Processing of the specified input file is terminated.

User Response: Change the JCL so that the input file contains the required input. Ensure that the specified DD points to a valid data set.

Pxmmmm041-I

xxxxxxxx

Explanation: An informational message indicating options and/or parameters that were processed by the language processor. There is no required system action.

Severity:

User Response: Check the message text, or contact BMC Support for additional information.

Pxmmmm042-W 

An nn-level message found and xxxxxxxx compile option specified.

Explanation: Sections of the COBOL listing needed by the language processor were missing due to nn-level messages.

Severity: The language processor does not append text to the object code, or creates a DDIO member.

User Response: Correct compiler errors and rerun the job.

Pxmmmm043-S

COBOL text for abend support will not be generated because of errors found.

Explanation: An error occurred while processing the listing, preventing the COBOL text from being generated.

Severity: The language processor continues but does not generate the COBOL text.

User Response: Check CWPERRM for previous error messages.

Pxmmmm044-S

DDIO member will not be generated because of errors found.

Explanation: An error occurred while processing the listing that prevented the DDIO member from being generated.

Severity: The language processor continues but does not generate the DDIO member.

User Response: Check CWPERRM for previous error messages.

Pxmmmm045-S

Program compiled with invalid options for CICS.

Severity: The CICSTEST parameter was specified and some invalid CICS compiler options were used. If command CICSTEST(OPTIONS(WARNING)) was used, then ‘x’ will be ‘W’ and RC is set to 4. If command CICSTEST(OPTIONS(SEVERE) was used, the ‘x’ will be 5 and the RC is set to 8.

Severity: The language processor sets a return code of 4 or 8 depending on the CICSTEST option value.

User Response: Check the specified compiler options, and either change the options or remove the CICSTEST parameter.

Pxmmmm046-W

Invalid CICS options: xxxxxxxx.

Explanation: The CICSTEST parameter was specified and some invalid CICS compiler options were used. This is a list of the options found invalid for a CICS compile.

Severity: The language processor continues and sets a return code of 4 or 8 depending on the CICSTEST option value.

User Response: Check the compiler options specified, and either change the options or remove the CICSTEST parameter.

Pxmmmm047-S

COBOL option VERB not specified.

Explanation: The required option VERB was not requested at compile time.

Severity: The language processor terminates.

User Response: VERB is a required compiler option and must be specified.

Pxmmmm048-S

COBOL option NOLST not specified.

Explanation: The required option NOLST was not specified at compile time.

Severity: The language processor terminates.

User Response: NOLST is a required compiler option and must be specified.

Pxmmmm049-S

COBOL option SOURCE not specified.

Explanation: The source listing was not requested at compile time.

Severity: The language processor terminates.

User Response: SOURCE is a required compiler option and must be specified.

Pxmmmm050-S

COBOL option XREF(FULL) not specified.

Explanation: The required option XREF(FULL) was not requested at compile time.

Severity: The language processor terminates.

User Response: XREF(FULL) is a required compiler option and must be specified.

Pxmmmm051-S

Postprocessor terminated; preprocessor must be used due to COPY SUPPRESS.

Explanation: The COPY SUPPRESS parameter was specified. The preprocessor must be used.

Severity: The language processor terminates.

User Response: Change the JCL to use the preprocessor or remove the SUPPRESS parameter from the COPY statements.

Pxmmmm052-I

Listing xxxxxxxx dated mm/dd/yyyy at hh.mm.ss successfully written to xxxxxxxx.

Explanation: The specified listing was successfully written to the xxxxxxxx DDIO file.

Severity: The language processor successfully terminates.

User Response: None required.

Pxmmmm053-I

Error writing listing xxxxxxxx dated mm/dd/yyyy at hh.mm.ss to xxxxxxxx.

Explanation: An error occurred during processing which prevented the specified listing from being written to the xxxxxxxx DDIO file.

Severity: The language processor terminates.

User Response: Refer to prior error messages for a more detailed explanation of the actual error. If this message is issued and no prior error messages exist, check the compiler return code and error messages.

Pxmmmm054-S

DDIOnnnn - text.

Explanation: An error occurred on the DDIO file. The text is an explanation of the return code specified in message Pxmmmm006-S.

Severity: The language processor terminates.

User Response: Refer to the User Response for message Pxmmmm006-S.

Pxmmmm055-S

CA-OPTIMIZER option MDMAP/MMAP not supported when used with COBOL Report Writer.

Explanation: A COBOL program with Report Writer has been compiled with CA-OPTIMIZER III MDMAP or CA-OPTIMIZER II MMAP. Not all DMAP information is contained in Merged DMAP area if the program contains Report Writer.

Severity: The language processor terminates.

User Response: Recompile the program without the MDMAP or MMAP compiler option.

Pxmmmm056-S

Error processing MDMAP line number nnnnnn, RC=nn.

Explanation: An error occurred while processing CA-OPTIMIZER merged DMAP information produced by CA-OPTIMIZER III MDMAP or CA-OPTIMIZER II MMAP. The error occurred on the line number specified.

Severity: The language processor continues, but suppresses the DDIO file.

User Response: Rerun the compiler specifying DMAP for OPTIMIZER III or MAP for OPTIMIZER II. This will turn off merged DMAP. Also, contact BMC Support with the listing and return code available. The following is a list of possible return codes: RC=01 - GETMAIN failed acquiring CWPC01MD work area. RC=02 - Exceeded length of level table. RC=03 - Locator cell type not recognized. RC=04 - File type not recognized. RC=05 - Picture clause character not recognized. RC=06 - Usage clause not recognized. RC=07 - Attribute flag (RODF) not recognized. RC=08 - Error reading DWRK file.

Pxmmmm057-S

Specified source file not formatted as a source file.

Explanation: The DDIO file specified in the JCL was not formatted as a source listing DDIO.

Severity: The language processor terminates.

User Response: Reformat as a source listing DDIO or allocate and format a new source listing DDIO.

Pxmmmm058-S

COBOL option BATCH specified.

Explanation: The batch compiler option is not supported.

Severity: The language processor terminates.

User Response: Rerun the compile using COBOL option NOBATCH.

Pxmmmm059-S

xxxxxxxx file contains more than 1 listing.

Explanation: The CWPPRTI input file contains more than one listing. The compiler option BATCH is not supported.

Severity: The language processor terminates after processing the first listing.

User Response: Remove all but the first listing from the CWPPRTI input file.

Pxmmmm060-S

COBOL option ATTRIBUTES(FULL) not specified.

Explanation: The required option ATTRIBUTES(FULL) was not specified at compile time.

Severity: The language processor issues an error message and ends.

User Response: ATTRIBUTES(FULL) is a required option and must be specified.

Pxmmmm061-S

COBOL option COPY(FULL) not specified.

Explanation: The required option COPY(FULL) was not specified at compile time.

Severity: The language processor issues an error message and ends.

User Response: COPY(FULL) is a required option and must be specified.

Pxmmmm063-S

An S-level message was found. Required portions of the listing are missing.

Explanation: An S-level error message was found during processing.

Severity: The language processor terminates.

User Response: Correct the compiler errors and resubmit.

Pxmmmm064-S

LIST option required when the OPTIMIZE option specified.

Explanation: A VS COBOL II program has been compiled with the OPTIMIZE and OFFSET options. The LIST option is required.

Severity: The language processor terminates.

User Response: Recompile the program with NOOPT and OFFSET or OPT and LIST. If postprocessing, the PROC($AOFF) option can be used. This may lead to unexpected results when debugging the DDIO member with Code Debug TSO or Code Debug CICS.

Pxmmmm065-I

Option PROC(BYPASS) has caused the Compuware Processor to be bypassed.

Explanation: The PROC(BYPASS) preprocessor option was specified.

Severity: The compiler is invoked, but the language processor is bypassed. No information is written to the DDIO file.

User Response: Remove the PROC(BYPASS) option or specify PROC(NOBYPASS) to allow the language processor to be invoked.

Pxmmmm066-I

The Compuware Processor has been bypassed due to the return code from the compiler.

Explanation: The CONDDDIO command specified a value that was less than the return code from the compiler.

Severity: The language processor is not invoked. No information is written to the DDIO file.

User Response: Correct the compiler errors, or remove the CONDDDIO command, or raise the value to invoke the language processor.

Pxmmmm067-S

Compiler xxxxxxxx not found.

Explanation: The specified compiler cannot be found with the current STEPLIB, JOBLIB, or task library concatenation.

Severity: The compiler specified by the LANGUAGE command cannot be found.

User Response: Change the LANGUAGE command to specify the correct compiler, or change your STEPLIB, JOBLIB, or task library concatenation.

Pxmmmm068-W

DDNAME xxxxxxxx not allocated. Include ignored.

Explanation: An INCLUDE command was supplied with a ddname that is not contained in the JCL.

Severity: The INCLUDE command is ignored.

User Response: Correct the ddname in the INCLUDE command, or add the DD card to the JCL.

Pxmmmm069-S

Error allocating xxxxxxxx.

Explanation: The language processor was unable to dynamically allocate the specified data set.

Severity: The language processor terminates.

User Response: Ensure that the data set is not exclusively allocated by another DD statement.

Pxmmmm070-S

Excessive number of parameters included. Include processing terminated.

Explanation: The number of specified language processor/compiler parameters exceeded the storage available to store the parameters.

Severity: No included set of options are processed.

User Response: This may be caused by having recursive parameter files included (i.e., member A includes member B, and member B includes member A). If this is true, change the incorrect INCLUDE command to eliminate the recursive condition.

Pxmmmm071-S

Include member xxxxxxxx(yyyyyyyy) not found.

Explanation: An INCLUDE command specified a member that does not exist in the specified data set.

Severity: The INCLUDE command is ignored.

User Response: Correct the INCLUDE command to specify the correct data set.

Pxmmmm072-S

Return code from function xxxxxxxx = yyyy at +nnnnnn.

Explanation: An unexpected error occurred in an internal routine. Return code yyyy was received at offset nnnnnn in module xxxxxxxx.

Severity: The language processor terminates.

User Response: Contact BMC Support.

Pxmmmm073-S

Unable to find compiler options in listing.

Explanation: The Options section of the compiler listing could not be found.

Severity: Processing may continue, but with unpredictable results.

User Response: Ensure that your LANGUAGE command specifies the appropriate language. Verify that you have the correct compiler and that the compiler is in your STEPLIB or link list.

Pxmmmm074-S

Unable to open xxxxxxxx dataset.

Explanation: The data set required by the language processor could not be opened.

Severity: The language processor terminates.

User Response: Ensure that the specified DD is included in your JCL.

Pxmmmm075-S

Specified value not numeric or too high: xxxxxxxxxx.

Explanation: An invalid language processor option value was specified.

Severity: The language processor terminates.

User Response: Correct the specified option in the CWPPRMO file or on the EXEC parameter.

Pxmmmm076-I

Assuming CONDERRL(n).

Explanation: The value specified for the CONDERRL command is invalid. Value n is assumed.

Severity: The language processor continues.

User Response: Correct the CONDERRL command in the CWPPRMO file or on the EXEC parameter and rerun the language processor.

Pxmmmm077-I

Assuming CONDDDIO(n).

Explanation: The value specified for the CONDDDIO command is invalid. Value n is assumed.

Severity: The language processor continues.

User Response: Correct the CONDDDIO command in the CWPPRMO file or on the EXEC parameter and rerun the language processor.

Pxmmmm078-I

The preprocessor has forced on option xxxxxxxxxxxxxxxxx.

Explanation: The required compiler option was not specified and was forced on by the preprocessor.

Severity: The language processor continues.

User Response: Add the required option in the CWPPRMO file or on the EXEC parameter to prevent the message.

Pxmmmm079-I

The preprocessor has deleted option xxxxxxxxxxxxxxxxx.

Explanation: This option conflicts with the required language processor options, so it is ignored.

Severity: The language processor continues.

User Response: No response is needed. If you delete the specified options, the preprocessor will no longer have to delete it. Removing the option from the CWPPRMO file on the EXEC parameter will prevent the message.

Pxmmmm080-I

PTFs applied are:

Explanation: Option SYSTEM(ZAP) or SYSTEM(PTF) was specified.

Severity: A list of all PTFs applied to this release of CSS are displayed.

User Response: No response is needed. Removing the option from the CWPPRMO file on the EXEC parameter will prevent the message.

Pxmmmm081-I

There are no PTFs applied.

Explanation: Option SYSTEM(ZAP) or SYSTEM(PTF) was specified, but there are no PTFs applied to the CSS library.

Severity: The language processor continues.

User Response: None.

Pxmmmm082-I

Only errors printed due to CONDERRL(nnn) option.

Explanation: The COBOL option CONDERRL(nnn) was specified, so only errors are printed.

Severity: The language processor continues.

User Response: No response is needed. If you want the entire error listing, remove option CONDERRL from the CWPPRMO file or the EXEC parameter.

Pxmmmm083-S

STOW error creating temporary SYSLIB member.

Explanation: The language preprocessor was attempting to add a copybook to a temporary PDS (CWPPDS2) and received an error. This may occur if the directory is full.

Severity: The language processor terminates.

User Response: Add a DD to the JCL for CWPPDS2 with larger space parameters. If necessary, contact BMC Support.

Pxmmmm084-I

The printed output will simulate option xxxxxxxxxxxxxxxxx.

Explanation: The preprocessor forced on a required option that affects the compiler listing. In an effort to produce the listing in the form that was requested, the preprocessor will simulate the compiler option.

Severity: The language processor continues.

User Response: None.

Pxmmmm085-S

Do not specify CLOSE=FREE on SYSPRINT DD.

Explanation: The CWPPRTI DD contains CLOSE=FREE.

Severity: The language processor terminates.

User Response: Remove CLOSE=FREE from CWPPRTI DD.

Pxmmmm086-S

SYSPRINT DD missing.

Explanation: The language processor requires a SYSPRINT DD.

Severity: The language processor terminates.

User Response: Add a SYSPRINT DD.

Pxmmmm087-S

SYSPRINT DD must have DISP=MOD when running CA-OPTIMIZER and xxxxxxxxxx.

Explanation: When using CA-OPTIMIZER, DISP=MOD must be coded on the SYSPRINT DD. The optimizer produces the banner page and then reopens the file to produce the listing. If MOD is not specified, the banner will be missing. The language processor expects to find the banner for optimized listings.

Severity: The language processor terminates.

User Response: Add DISP=MOD to the SYSPRINT DD.

Pxmmmm088-W

SWAREQ service failed when inquiring about SYSPRINT, please notify COMPUWARE.

Explanation: The IBM-supplied SWAREQ service is called by the language processor to find the attributes for the SYSPRINT file. An unexpected error occurred during the SWAREQ.

Severity: The language processor terminates.

User Response: Contact BMC Support.

Pxmmmm089-S

xxxxxxxx cannot be allocated as SYSIN, SYSOUT, or DUMMY.

Explanation: The DD represented by xxxxxxxx cannot be allocated to SYSIN, SYSOUT, or DUMMY.

Severity: The language processor terminates.

User Response: Change the DD for xxxxxxxx so it is not allocated to SYSIN, SYSOUT, or DUMMY.

Pxmmmm090-S

SWAREQ GETMAIN failed, please increase REGION.

Explanation: A GETMAIN issued in preparation of a SWAREQ failed.

Severity: The language processor terminates.

User Response: Increase your REGION parameter.

Pxmmmm091-S

CA-OPTIMIZER will not tolerate SYSPRINT allocated as a PDS member when running xxxxxxxxxx.

Explanation: This CA-OPTIMIZER release does not support SYSPRINT being allocated to a PDS member.

Severity: The language processor terminates.

User Response: Change the JCL so SYSPRINT is not allocated to a PDS member.

Pxmmmm092-S

SYSPRINT cannot be allocated to tape.

Explanation: The language processor requires the SYSPRINT file to be allocated to DASD.

Severity: The language processor terminates.

User Response: Change your JCL so SYSPRINT is not allocated to a magnetic tape unit.

Pxmmmm093-I

Possible LSTONLY compiler option used

Explanation: The LSTONLY option was specified for VS COBOL. This option is unsupported.

Severity: The language processor terminates.

User Response: Change the compiler STEPLIB library to reference a supported compiler. Rerun the language processor.

Pxmmmm094-W

Incorrect/conflict option(s) passed to compiler.

Explanation: An option was passed to the compiler that is either invalid or in conflict with another option. This message is accompanied by message Pxmmmm095-W.

Severity: The language processor does not pass the option to the compiler and processing continues.

User Response: Remove the invalid option.

Pxmmmm095-W

xxx. . .xxx.

Explanation: An invalid compiler option was specified. xxxx is the compiler message. Because the language processor forces the correct options, this message does not appear in the compiler listing, but is presented in the CWPERRM DD for reference.

Severity: The language processor continues.

User Response: Remove the invalid option.

Pxmmmm096-I

The preprocessor has bypassed the dummy compile due to option $NO.

Explanation: COBOL option PROC($NO) was specified either in the CWPPRMO file or on the EXEC parameter. This causes the preliminary compilation to be bypassed.

Severity: The language processor continues.

User Response: Ensure that all required compiler options are specified. Refer to the appropriate language processing section in this space. This space lists the required options by compiler.

Pxmmmm097-W

The preprocessor has bypassed the generated lines support due to option $NG.

Explanation: COBOL option PROC($NG) has been specified. This causes the GEN support processing to be bypassed. GEN support handles suppressed listing lines due to COPY SUPPRESS, PRINT NOGEN or OFF, or %NOPRINT.

Severity: The language processor continues.

User Response: No response is necessary, unless your source contains a COPY SUPPRESS, PRINT NOGEN or OFF, or %NOPRINT. If your source contains these options, either remove the suppress statements from your source or remove the PROC($NG) option.

Pxmmmm098-S

The SYSIN dataset is empty.

Explanation: The SYSIN source file is empty.

Severity: The language processor terminates.

User Response: Change your JCL so SYSIN references the correct source file.

Pxmmmm100-W

CONDERRL does not support the language used.

Explanation: The CONDERRL(n) option was specified but is not available for the compiler used. CONDERRL is only supported for OS/VS COBOL with CA-OPTIMIZER.

Severity: The language processor continues without CONDERRL.

User Response: Either remove the CONDERRL parameter or change your JCL to use CA-OPTIMIZER for VS COBOL.

Pxmmmm101-W

An “(“ expected after xxxxxxxxxx. Skipping to next valid option.

Explanation: The parser was looking for a subparameter for xxxxxxxx and failed to find a parenthesis ‘(’.

Severity: The specified option is discarded and processing continues with the next valid option.

User Response: Add the missing subparameter or parenthesis for the specified option.

Pxmmmm102-S

No ESD information. Check assembly options.

Explanation: The external symbol dictionary could not be found in the listing.

Severity: The language processor terminates.

User Response: Specify ESD as an assembly option and rerun the job.

Pxmmmm103-S

COBOL option GEN not specified

Explanation: The required option GEN was not specified.

Severity: The language processor terminates.

User Response: GEN is a required compiler option and must be specified.

Pxmmmm104-S

COBOL option NONUMBER not specified

Explanation: The required option NONUMBER was not specified at compile time.

Severity: The language processor terminates.

User Response: NONUMBER is a required compiler option and must be specified.

Pxmmmm105-S

COBOL option OPTIMIZE specified

Explanation: The required COBOL option OPTIMIZE was not specified at compile time.

Severity: The language processor terminates.

User Response: OPTIMIZE is a required compiler option and must be specified.

Pxmmmm106-S

COBOL option TEST specified.

Explanation: The required option TEST was not specified at compile time.

Severity: The language processor terminates.

User Response: TEST is a required compiler option and must be specified.

Pxmmmm107-S

This compiler or assembler is not supported.

Explanation: The compiler or assembler that was used is not supported by the language processor.

Severity: The language processor terminates.

User Response: Change the compiler STEPLIB library to reference a supported compiler. Rerun the language processor.

Pxmmmm108-S

xxxxxxxx - option not supported. Processing terminated.’

Explanation: The language processing option that was specified is not supported.

Severity: The language processor terminates.

User Response: Remove the invalid option.

Pxmmmm109-W

LIST option should be specified when OPTIMIZE is specified.

Explanation: This warning indicates that OFFSET was used with OPTIMIZE, but the LIST compiler option is recommended.

Severity: Postprocessing continues.

User Response: Change the compiler option to LIST and rerun the language processor.

Pxmmmm110-S

Usage of xxxxxxxx on stmt nnnnnnnn not supported. Processing terminated.

Explanation: The specified Assembler Language Processor does not support any of the reserved words: ACONTROL, CATTR, or ALIAS.

Severity: The language processor terminates.

User Response: Modify the program or contact BMC Support.

Pxmmmm111-I

No Procedure Division found in listing.

Explanation: No Procedure Division was found in the VS COBOL II or COBOL/370 nested COBOL program.

Severity: Processing may continue, but with unpredictable results.

User Response: None required.

Pxmmmm112-W

Enhanced FIND is not supported with nested COBOL programs. Support is disabled.

Explanation: Enhanced FIND is not supported in nested COBOL programs.

Severity: Processing will continue, but the enhanced FIND feature will be disabled.

User Response: None required.

Pxmmmm113-W

Pxmmmm114-S

COBOL for MVS and VM reserved word found: xxxxxxxxxxxxx.

Explanation: A reserved word was found that is not supported when compiling with COBOL for MVS and VM.

Severity: The language processor terminates.

User Response: Bypass language processor viewing for this program or remove the object-oriented extensions from the source.

Pxmmmm115-S

Pxmmmm116-S

COBOL option PGMNAME(COMPAT) not specified.

Explanation: The postprocessor requires compiler option PGMNAME(COMPAT).

Severity: The postprocessor terminates processing.

User Response: Specify compiler option PGMNAME(COMPAT).

Pxmmmm117-I

xxxxxxxx document captured in dataset yyyy volume zzzzz.

Explanation: A CWPCAP DD statement was specified in your JCL. This caused the language processor to capture the required documentation to send to BMC Support for problem resolution. Document xxxxxxxx was written to data set yyyy on volume zzzz.

Severity: The language processor continues processing.

User Response: Send volume zzzz to BMC Support for problem resolution. If you do not have an outstanding language processor problem, remove the CWPCAP DD statement from your JCL.

Pxmmmm118-S

Error occurred capturing dataset xxxx RC=yy.

Explanation: A CWPCAP DD statement was specified in your JCL. This caused the language processor to attempt to capture all the required documentation. An error occurred when trying to capture data set xxxx. The error is indicated by the return code. Possible return codes are: RC=04 - Dynamic allocation error RC=08 - Error opening capture file RC=OC - Error writing capture file RC=10 - GETMAIN error RC=14 - Utility error RC=18 - LOADLIB error

Severity: The language processor continues attempting to gather other documentation.

User Response: Before sending documentation, notify BMC Support. Manual effort may be required to send missing documentation. If DOCUMENT=LOADLIB and any CSS libraries are in the link list or LPA, specify these data sets in the STEPLIB.

Pxmmmm119-S

PL/I option(s) (OFFSET and STORAGE) or OBJECT not specified.

Explanation: An OFFSET map and a STORAGE map, or an OBJECT map, is required.

Severity: The language processor terminates.

User Response: Specify either (OFFSET and STORAGE) or Listing OBJECT options.

Pxmmmm120-S

PL/I option MAP not specified.

Explanation: An Internal Storage Map is required.

Severity: The language processor terminates.

User Response: Specify MAP as a compiler option.

Pxmmmm121-S

PL/I option XREF(FULL) not specified.

Explanation: A cross-reference is required.

Severity: The language processor terminates.

User Response: Specify XREF(FULL) as a compiler option.

Pxmmmm122-S

PL/I option LIST not specified.

Explanation: An alternate reserved word table was requested for a PL/I compile.

Severity: The language processor terminates.

User Response: Specify LIST as a compiler option.

Pxmmmm123-S

PL/I option ATTRIBUTES(FULL) not specified.

Explanation: The required option ATTRIBUTES(FULL) was not specified at compile time.

Severity: The language processor terminates.

User Response: Specify ATTRIBUTES(FULL) as a compiler option.

Pxmmmm124-S

PL/I option AGGREGATE not specified.

Explanation: The required option AGGREGATE was not specified at compile time.

Severity: The language processor terminates.

User Response: Specify AGGREGATE as a compiler option.

Pxmmmm125-S

PL/I option SOURCE not specified.

Explanation: The source listing was not requested at compile time.

Severity: The language processor terminates.

User Response: Specify SOURCE as a compiler option.

Pxmmmm126-S

PL/I option OFFSET not specified.

Explanation: The required option OFFSET was not specified at compile time.

Severity: The language processor terminates.

User Response: Specify OFFSET as a compiler option.

Pxmmmm127-S

PL/I option STORAGE not specified.

Explanation: The required option STORAGE was not requested at compile time.

Severity: The language processor terminates.

User Response: Specify STORAGE as a compiler option.

Pxmmmm128-W

Dataname xxxxxxxx not found. It may exceed 30 characters and was not processed fully.’

Explanation: Datanames longer than 30 characters are supported only for PL/I compiler releases 2.3 and above, PL/I ADCYCLE, and PL/I for MVS and VM.

Severity: The language processor terminates.

User Response: If possible, use compiler releases 2.3 and later.

Pxmmmm129-S

PL/I listing not complete.

Explanation: Message Pxmmmm119 - Pxmmmm121 or Pxmmmm007 was issued or, one or more of the PL/I sections could not be found. A previous message will indicate what section is missing.

Severity: The language processor terminates.

User Response: Check for messages Pxmmmm119 - Pxmmmm121 or Pxmmmm007, or missing PL/I section in the listing. Add missing compiler options as necessary. If neither condition is found, contact BMC Support.

Pxmmmm130-S

Postprocessor terminated; preprocessor must be run due to %NOPRINT.

Explanation: An attempt was made to postprocess a %NOPRINT statement. The postprocessor is not designed to handle %NOPRINT.

Severity: The language processor terminates.

User Response: Use the preprocessor to process the %NOPRINT statement.

Pxmmmm131-S

Preprocessor terminated; possible Macro Generated %NOPRINT encountered.

Explanation: During preprocessing, a %NOPRINT was found that the language processor could not handle. Most likely the %NOPRINT was generated within a macro.

Severity: The language processor terminates.

User Response: You can use the preprocessor to process the %NOPRINT statement, or you can remove the %NOPRINT from the macro. Please refer to the BMC AMI Common Shared Services User/Reference space for additional information.

Pxmmmm132-S

Internal error: Proc xxxxxxxx. Contact BMC Support.

Explanation: The processor detected an internal error processing the Variable Storage Map area of a PL/I listing.

Severity: The language processor terminates.

User Response: Contact BMC Support.

Pxmmmm133-S

Postprocessor terminated; multiple listings detected in CWPPRTI DD.

Explanation: Multiple unique and separate PL/I source programs compiled in a single batch compilation are not supported.

Severity: The language processor terminates.

User Response: Compile each source program separately.

Pxmmmm134-S

Postprocessor terminated; first statement not PROCEDURE.

Explanation: The PL/I Language Processor could not identify a PROC, PROCEDURE, or PACKAGE statement as the first valid language statement syntax in the user program.

Severity: The language processor terminates.

User Response: Correct the user program so that the first PL/I language statement is one of PROC, PROCEDURE, or PACKAGE. One or more syntactically correct PL/I comment statements or compiler directives proceeding the first PL/I language statement are permitted.

Pxmmmm135-S

Usage of PL/I option "nnnn" is not supported.

Explanation: When processing a PL/I program, a compiler option was encountered that was specified by the user but is not supported by the PL/I Language Processor. Certain options are not supported because they alter the compiler output in some way that cannot be handled by the PL/I Language Processor.

Severity: Processing of the PL/I program or listing ends and a return code of 8 is issued.

User Response: Remove the option specified in the error message from the EXEC PARM field, PL/I *PROCESS lines, or options list and resubmit the job.

Pxmmmm150-S

Assembler option XREF not specified.

Explanation: A cross-reference is required.

Severity: The Assembler postprocessor terminates.

User Response: Specify XREF as an assembler option.

Pxmmmm151-S

Postprocessor terminated. The preprocessor must be used due to PRINT OFF/NOGEN.

Explanation: A PRINT OFF or NOGEN was found in the listing but the preprocessor was not used.

Severity: The language processor terminates.

User Response: Either change your JCL to use the preprocessor or remove the PRINT OFF and/or PRINT NOGEN from the source.

Pxmmmm152-S

Assembler listing not complete.

Explanation: Message (Pxmmmm150 or Pxmmmm007) was issued, or one or more of the Assembler sections could not be found.

Severity: The Assembler postprocessor terminates.

User Response: Check for message Pxmmmm150 or Pxmmmm007 or missing Assembler section in the listing. If a section is missing, ensure that the correct assembly options are specified. If the options are correct, contact BMC Support.

Pxmmmm153-W

Operand ONE does not use a base or an index register specified.

Explanation: The language processor option DIAGNOSE(LOW-CORE) was specified and an instruction was found that has both the base register and the index register (where applicable) coded as zero.

Severity: The Assembler postprocessor sets the return code to 4.

User Response: Change the source code to eliminate the possible problem, change the language processor option to NOLOW-CORE, or ignore the warning because the source code is correct.

Pxmmmm154-W

Operand TWO does not use a base or an index register specified.

Explanation: The language processor option DIAGNOSE(LOW-CORE) was specified and an instruction was found that has both the base register and the index register (where applicable) coded as zero.

Severity: The Assembler postprocessor sets the return code to 4.

User Response: Change the source code to eliminate the possible problem, change the language processor option to NOLOW-CORE, or ignore the warning because the source code is correct.

Pxmmmm155-W

RX instruction uses an index register but has no base register.

Explanation: The language processor option DIAGNOSE(ESA-INDEX) was specified, and an instruction was found that has an index register and no base register coded.

Severity: The Assembler postprocessor sets the return code to 4.

User Response: Change the source code to eliminate the possible problem, change the language processor option to NOESA-INDEX, or ignore the warning because the source code is correct.

Pxmmmm220-S

COBOL option LIST(0,999999) not specified

Explanation: A full program listing must be displayed.

Severity: The language processor receives a RC=8. Processing may continue, but with unpredictable results.

User Response: Specify the LIST option.

Pxmmmm221-S

COBOL option PMAP or CLIST not specified

Explanation: A Procedure Map (PMAP) or condensed listing (CLIST) is required.

Severity: The language processor terminates.

User Response: Specify appropriate compiler option (PMAP or CLIST).

Pxmmmm222-S

COBOL option LISTX or CLIST not specified

Explanation: The LISTX or CLIST compiler option is required.

Severity: The language processor terminates.

User Response: Specify the appropriate compiler option LISTX or CLIST.

Pxmmmm223-S

COBOL option MAP(FULL) not specified

Explanation: Required COBOL compiler option MAP(FULL) was not specified.

Severity: The language processor terminates.

User Response: Specify the MAP(FULL) compiler option.

Pxmmmm224-S

COBOL option DMAP not specified

Explanation: Required COBOL compiler option DMAP was not specified.

Severity: The language processor terminates.

User Response: Specify the DMAP compiler option.

Pxmmmm225-S

COBOL option XREF or SXREF not specified

Explanation: Required COBOL compiler option XREF or SXREF was not specified.

Severity: The language processor terminates.

User Response: Specify the appropriate compiler option, XREF or SXREF.

Pxmmmm227-S

COBOL option XREF(LONG) not specified.

Explanation: The required option XREF(LONG) was not specified.

Severity: The language processor issues an error message and ends.

User Response: Specify the XREF(LONG) compiler option. It is required.

Pxmmmm228-S

COBOL option NAME specified.

Explanation: The required option NAME was not specified.

Severity: The language processor issues an error message and ends.

User Response: Specify the NAME compiler option. It is required.

Pxmmmm229-S

COBOL option SOURCE(1) not specified.

Explanation: The required option SOURCE was not specified.

Severity: The language processor issues an error message and ends.

User Response: Specify the SOURCE compiler option. It is required.

Pxmmmm230-S

SYSMDECK is allocated incorrectly, attempted reallocation failed.

Explanation: SYSMDECK was not properly allocated. CSS will try to reallocate SYSMDECK with the correct attributes, however this reallocation failed.

Severity: The language processor issues an error message and ends.

User Response: Please report this error to BMC Support.

Pxmmmm231-S

No verbs found in COBOL 5.X listing.

Explanation: An Enterprise COBOL 5.X or higher listing was processed and no verbs were found in the listing.

Severity: The language processor issues an error message and ends.

User Response: Please report this error to BMC Support.

Pxmmmm257-E

Cannot find typedef tttttttt line:col.

Explanation: The C language processor cannot find the definition of typedef ‘tttttttt’. The typedef is used at the specified line and column in the Source section of the listing.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: Please report this error to BMC Support.

Pxmmmm258-E

Cannot determine size of line:col.

Explanation: The C language processor needs to evaluate the ‘sizeof’ function for an expression, but is unable to determine the underlying type of the expression. The expression occurs at the specified line and column in the Source section of the listing.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: Please report this error to BMC Support.

Pxmmmm259-E

Cannot calculate constant expression line:col.

Explanation: The C language processor needs to evaluate the value of some expression, but is unable to do so. The expression occurs at the specified line and column in the Source section of the listing.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: Please report this error to BMC Support.

Pxmmmm260-E

Variable xxxxxxxx not found.

Explanation: The C language processor has found the named variable in the Storage Offset section of the listing, but did not find any definition of that variable in the Source section of the listing.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: Please report this error to BMC Support.

Pxmmmm261-S

Internal error nnnnnnnn.

Explanation: The C language processor has encountered a logic error in its own code. This message may be accompanied by other messages that specify the location of the error.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: Please report this error to BMC Support.

Pxmmmm263-S

Illegal character line:col.

Explanation: The C language processor has detected what appears to be an identifier at the specified line and column of the Source section of the listing, but the identifier begins with a character that is illegal for an identifier.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: Please report this error to BMC Support.

Pxmmmm264-W

( expected xxxxxxxx.

Explanation: The options passed to the C language processor, through the CWPPRMO data set or through the EXEC PARM= string, are not syntactically correct. A left parenthesis was expected but not found. The text “xxxxxxxx” describes the context in which the left parenthesis was expected; for example, “after OUTPUT”.

Severity: The language processor continues to process the listing, and will write it to DDIO if there are no errors more severe than this one. The processor will complete with return code 4.

User Response: Correct the syntax of the option.

Pxmmmm265-S

) expected

Explanation: The options passed to the C language processor, through the CWPPRMO data set or through the EXEC PARM= string, are not syntactically correct. A right parenthesis was expected, to balance a previous left parenthesis, but no right parenthesis was found.

Severity: The language processor continues to process the listing, and will write it to DDIO if there are no errors more severe than this one. The processor will complete with return code 4.

User Response: Correct the syntax of the option.

Pxmmmm266-E

The following listing line was not recognized:.

Explanation: While scanning the compiler listing, in some section after the Source section, the C language processor encountered a listing line in an unexpected format. The line in question is displayed in message 271, following this message.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: Please report this error to BMC Support.

Pxmmmm267-S

No source listing.

Explanation: The C language processor never found a line it recognized as the page header line of a supported C compiler.

Severity: The language processor terminates with return code 8. It writes nothing to DDIO.

User Response: Check that you are using a supported C compiler, and (if using the postprocessor) that you have specified a valid C compiler listing in the DD statement for CWPPRTI.

Pxmmmm268-E

Unknown macro directive xxxxxxxx.

Explanation: The C language processor has encountered a C-preprocessor directive (#xxxxxxxx) that it does not recognize.

Severity: The language processor will continue to process the rest of the listing, but will eventually terminate with return code 8 or higher. The listing will not be written to DDIO.

User Response: You may be using a version of the C compiler not supported by the C language processor. If you can avoid using the unknown preprocessor directive, the C language processor may be able to complete successfully. If you are using a supported version of the C compiler, please report this problem to BMC Support.

Pxmmmm270-E

Incompatible compile option xxxxxxx found, terminating.

Explanation: The C language processor found a compiler option in effect that precludes it from processing the listing at all. The option PPONLY is an example.

Severity: The C language processor terminates with return code 16.

User Response: Either remove the incompatible option, or use the C compiler stand-alone for compiling with that option.

Pxmmmm271-S

xxxxxxxx xxxxxxxx.

Explanation: This message number is used to display a listing line that was involved in a previously reported error.

Severity: As required for the previously reported error.

User Response: See the preceding message for the nature and severity of the error.

Pxmmmm272-S

Internal DDIO image error nnnnnnnn.

Explanation: The C language processor has detected an internal error while attempting to write the listing to DDIO. The error is in the internal structure of the processor’s control blocks; the DDIO file itself is not in error.

Severity: The C language processor terminates with return code 16.

User Response: Please report this problem to BMC Support.

Pxmmmm274-W

Extraneous characters in option xxxxxxxx.

Explanation: The options passed to the C language processor, through the CWPPRMO data set or through the EXEC PARM= string, are not syntactically correct. Characters were found that did not form any part of a recognized option.

Severity: The language processor continues to process the listing, and will write it to DDIO if there are no errors more severe than this one. The processor will complete with return code 4.

User Response: Correct the syntax of the option.

Pxmmmm275-W

Unable to add timestamp to object deck.

Explanation: The BMC AMI language processor was unable to add its internal information (including a compile timestamp) to the object deck produced by the compiler. Depending on the language, Code Debug TSO may be unable to locate the listing for this program unless this problem is corrected.

Severity: The processor continues to completion, and writes the listing to DDIO, then terminates with return code 4.

User Response: Check that your DD for CWPLOAD specifies the object deck that corresponds to the listing specified in your DD for CWPPRTI. If this does not solve the problem, please report the problem to BMC Support.

Pxmmmm276-I

Object deck not updated because option PROCESSOR($NIDR) was coded.

Explanation: The C language processor has bypassed updating the object deck produced by the compiler because you included the PROCESSOR($NIDR) option in the CWPPRMO data set or in the ‘EXEC PARM=’ string.

Severity: The C language processor runs to completion and terminates with return code 0.

User Response: None.

Pxmmmm277-S

LANGUAGE(xxxxxxxx) not recognized. Use CMVS or C390.

Explanation: In the options for the C language processor, you included the option “LANGUAGE(xxxxxxxx)” to specify which C compiler the language processor should invoke. The text you put between the parentheses was not CMVS or C390.

Severity: The C language processor terminates with return code 16.

User Response: Specify CMVS to invoke the C/C++ for MVS compiler (program CBC320PP) or specify C390 to invoke a version of the C/C++ for OS/390 compiler (program alias CBCDRVR).

Pxmmmm278-S

LP shared directory for member name longer than 8: cccccccc

Explanation: You are attempting to write a “C” listing, with a name (cccccccc) longer than 8 characters, to an ordinary DDIO file. Only an LP database attached to a shared directory can support a name longer than 8 characters. See the “C Language Processor” section of the BMC AMI Shared Services User/Reference space for how the name of a “C” listing is selected. See “Batch File Utility CWDDLPUT” in the BMC AMI Common Shared Services User/Reference space for how to create an LP shared directory.

Severity: The language processor terminates with an error. The listing is not written to DDIO.

User Response: Either use a shorter name (see “C Language Processor” in the BMC AMI Common Shared Services User/Reference space) for how to select a name), or create an LP shared directory with attached LP databases to hold this member.

Pxmmmm279-S

dddddddd must be RECFM F(B)(A) LRECL03 or 9V(B)(A) LRECL >= 137.

Explanation: You are attempting to write the compiler listing to a DD name‘dddddddd’ (usually SYSCPRT) which has the wrong DCB characteristics for a listing.

Severity: The language processor terminates with an error. The listing is not written to DDIO.

User Response: Change the DD statement and rerun the job.

Pxmmmm301-S

Unable to identify root word for nnnnnnnn.

Explanation: The COBOL alternative reserved word table has found a reserved word it cannot recognize.

Severity: The language processor continues, but you may receive compiler errors.

User Response: Review your reserved word table and make sure you are using a correct reserved word.

Pxmmmm302-W

Push/Pop table limit exceeded.

Explanation: The Assembler program exceeded the limit set for PUSH PRINT and there was no matching POP PRINT.

Severity: The language processor continues.

User Response: Contact BMC Support.

Pxmmmm304-S

C++ compiler is not yet supported.

Explanation: The C language processor has detected that you are invoking the C++ compiler, or (postprocessor) that the listing you are processing was produced by the C++ compiler.

Severity: The language processor terminates with return code 8 or 16.

User Response: Do not attempt to use the BMC AMI C language processors in connection with C++.

Pxmmmm305-S

Compiler option xxxxxxxx is required.

Explanation: The C language postprocessor has discovered that the listing you specified in the DD for CWPPRTI was compiled without one or more of the compiler options required by the postprocessor. The required options are EXPMAC, SOURCE, SHOWINC, LIST and XREF.

Severity: The C language postprocessor terminates with return code 8.

User Response: Recompile your program using all the required options.

Pxmmmm306-S

Dummy compile failed, RC = xxxxxxxx.

Explanation: The C language preprocessor attempts a small dummy compile to determine the net effect of the compiler options you have requested combined with the compiler options it must force on. This dummy compile has failed with a return code greater than 4.

Severity: The C language preprocessor terminates with return code 16.

User Response: Review the compiler options you have requested for correctness by C standards. If you cannot discover any error, please report this problem to BMC Support.

Pxmmmm307-E

Recursive xxxxxxxx statement found for xxxxxxxx.

Explanation: A copy or include member contains a recursive reference to the same member. Nested copy or include members that are recursive in nature are not supported.

Severity: The CSS language preprocessor terminates the compilation.

User Response: Remove the recursive references from the source programs and resubmit the job.

Pxmmmm308-I

DBMODEL DYNCREATE=YES specified; dynamic database creation invoked, processing continues.

Explanation: CWPDDIO was specified as a shared directory, and not enough space was found on the attached databases to add the new source listing member. A DBMODEL with DYNCREATE=YES exists for this shared directory, and the dynamic database process was invoked, creating a new database, attaching it to the shared directory, and creating the new source member.

Severity: The language processor continues, but a return code of 4 is set.

User Response: None required.

Pxmmmm309-I

Member name created by truncating PROD name nnnnnnnn

Explanation: PL/I PROC name exceeds 8 characters. MEMBER name created by truncation of PROC name.

Severity: The language processor continues.

User Response: None required.

Pxmmmm310-W

Pointer problem found in HASH TABLE BLK nnnnnnnn

Explanation: PL/I labels cannot be resolved correctly.

Severity: The language processor terminates.

User Response: Check syntax of PL/I code. Check compiler return codes, report problem to BMC Support.

Pxmmmm311-W

DMAP record: xxxxxxxx

Explanation: This message was produced in conjunction with another error message.

Severity: The language processor terminates.

User Response: (refer to other associated message)

Pxmmmm312-W

$NIDR was specified, object deck not updated with time stamp

Explanation: User requested that the OBJECT deck not be updated by use of the $NIDR LP option, no identifier information is placed within the OBJECT deck. Debugging and source viewing may have problems locating source.

Severity: The language processor continues.

User Response: You can remove the $NIDR override if company standards warrants.

Pxmmmm313-S

A detached database was specified on CWPDDIO; the database must be attached to a shared directoryExplanation: The source listing database specified in the DD for CWDDIO is not attached to a shared directory. A source listing database must be attached to a shared directory when used as the CWPDDIO output file.

Severity: The language processor terminates with return code 8.

User Response: Select a source listing database that is attached to a shared directory; or, attach this source listing database to a shared directory.

Pxmmmm314-I

xxxxxxxx

Explanation: An informational DDIO file message has been issues.

Severity: The language processor continues.

User Response: None required.

Pxmmmm315-W

Split datanames not supported on line xx

Explanation: A COBOL dataname displays on two distinct lines.

Severity: The language processor continues, but a return code of 4 is set.

User Response: Rearrange the dataname so it fits on a single line within the legal margins. Then, resubmit the job for compilation and language processing.

Pxmmmm316-I

Listing mmmmmmmm processed on MM/DD/YYYY at HH:MM:SS

Explanation: The language processor execution date and time are displayed.

Severity: The language processor completes successfully.

User Response: None required.

Pxmmmm317-W

IDENTIFY data not written to object deck

Explanation: The OBJECT deck was not updated with the 'IDENTIFY' record.

Severity: The language processor continues, a non-zero RC is returned.

User Response: Check LP JCL, check compiler options, please report this error to BMC Support.

Pxmmmm318-W

IDENTNO was specified, IDENTIFY data was not written to object deck

Explanation: USER forbids IDENTIFY record to be written.

Severity: The language processor continues.

User Response: None required.

Pxmmmm319-W

IDENTIFY data can not be written; compiler option CSECT is required for that

Explanation: The OBJECT deck is not updated with the IDENTIFY record, compiler option 'CSECT' is required for updates to take place.

Severity: The language processor continues.

User Response: Change the 'CSECT' option if company standards warrants.

Pxmmmm320-I

SD-wide AUTOLOCKMAX and/or DUPMAX values applied to one or more duplicate members

Explanation: The shared directory has one or both of the AUTOLOCKMAX and/or DUPMAX values set.

Severity: Any existing duplicate (same program name) members were first adjusted (delete/lock/unlock) as needed, per the values set.

User Response: None required.

Pxmmmm321-S

GETMAIN failure with a return code X’rr’ from mmmmmmmmm+xxxx for length X’ssssssss

Explanation: GETMAIN failure, could not obtain needed storage space.

Severity: GETMAIN failure with a return code X’rr’ from mmmmmmmmm+xxxx for length X’ssssssss’.

User Response: Increase region size or if that is not sufficient, contact BMC Support.

Pxmmmm322-S

Increase region size or contact BMC Support

Explanation: GETMAIN failure, could not obtain needed storage space.

Severity: GETMAIN failure with a return code X’rr’ from mmmmmmmmm+xxxx for length X’ssssssss’.

User Response: Increase region size or if that is not sufficient, contact BMC Support.

PTFPRNT01-I

List of applied PTFs.

Explanation: Informational message.

Severity: Applied PTFs are listed to the right of the message text.

User Response: None required. 

Pxmmmm323-W

Unable to allocate one or more databases attached to the shared directory

Explanation: While building the list of attached databases to be used, unable to allocate one (or more) of the databases.

Severity: Processing continues.

User Response: Run a DIRX utility function on the shared directory, check the attached databases.

Pxmmmm324-S

Total duplicate versions of this program may exceed shared directory buffer limit

Explanation: The total number of duplicate programs (programs with the same name) exceeds the allocated buffer size used in the shared directory processing.

Severity: The processing terminates.

User Response: Delete older versions of the programs if no longer needed.

Pxmmmm325-W

Unable to complete the ALMAX/DUPMAX duplicate adjustment - utility VERIFY function recommendedExplanation: While processing the existing duplicate programs (same program name) in the shared directory, one or more problems/errors occurred with a member action (delete/lock/unlock).

Severity: The members in error are skipped and processing continues.

User Response: Run the CSS VERIFY (or EXAMINE) utility function against the shared directory to identify potential problems. Contact BMC Support.

Pxmmmm326-W

Assembler program name longer than 8, truncated to 8 for classic DDIO - use shared directory for longname support

Explanation: The newer assembler languages support CSECT names longer than 8 characters, but a classic DDIO file cannot handle them.

Severity: Program name is truncated to 8 characters, processing continues.

User Response: Create a source shared directory and databases to handle the full names longer than 8 characters.

Pxmmmm327-I

Language processor running zIIP enabled

Explanation: The language processor is eligible to execute a portion of its processing on a zIIP processor. This is just an informational message.

Severity: None.

User Response: None required.

Pxmmmm328-I

zIIP time used xxxx.xxx CPU seconds, storage used xx MB

Explanation: The amount of CPU time that was executed on a zIIP processor is reported, as well as the amount of memory used to buffer the file I/O.

Severity: None.

User Response: None required.

Pxmmmm329-I

zIIP processing is unavailable

Explanation: During language processor initialization it was discovered that zIIP processing is not available.

Severity: The job executes normally, but will not use any zIIP processors.

User Response: If the intention is not to use zIIP processing, no response is required. If zIIP processing is desired, then check the following areas for reasons why zIIP processing was unavailable:

Pxmmmm330-S

DBMODEL CREATE invoked, error trying to create the new database.

Explanation: Error occured during database creation using supplied DBMODEL parameters.

Severity: Database is not created.

User Response: Evaluate and adjust DBMODEL parameters.

Pxmmmm331-I 

Listing mmmmmmmm assigned member number yy

Explanation: Listing was created and assigned the reported member number.

Severity: None.

User Response: None required.

Pxmmmm332-I

Listing(s) successfully written out to DDIO

Explanation: Listing was successfully written out to DDIO.

Severity: None.

User Response: None required.

Pxmmmm333-I

Listing mmmmmmmm dated MM/DD/YYYY at HH:MM:SS

Explanation: Listing was created and dated with the reported date and time.

Severity: None.

User Response: None required.

Pxmmmm334-S

SYSMDECK was allocated with DISP of MOD. This will cause the member to be generated incorrectly.

Explanation: The SYSMDECK DD was allocated with a disposition of MOD.

Severity: The processing terminates.

User Response: Allocate SYSMDECK with a different disposition.

Pxmmmm335-I

Identical member/date/time already in shared directory and DUPMAX GT 1. New member not added.

Explanation: When adding a member to a shared directory, we found a matching member already existed.

Severity: The member is not added to shared directory.

User Response: None required. The member was already in the shared directory.

Pxmmmm336-W

ESS=YES specified, but no CWPLOAD object specified. Change to ESS=NO or specify CWPLOAD object.

Explanation: An ESS postprocess was started without an object to add the listing to.

Severity: ESS is turned off and processing continues.

User Response: Remove option ESS(YES) or specify CWPLOAD object.

Pxmmmm337-W

PL/I option OBJECT not specified. OBJECT must be specified when ESS=YES.

Explanation: Option ESS(YES) was specified, but compile option OBJECT was not specified.

Severity: ESS is turned off and processing continues.

User Response: Specify option OBJECT to create ESS listing.

Pxmmmm338-W

PL/I option GOFF not specified. GOFF must be specified when ESS=YES.

Explanation: Option ESS(YES) was specified, but compile option GOFF was not specified.

Severity: ESS is turned of and processing continues.

User Response: Specify option GOFF to create ESS listing.

Pxmmmm339-E

Postprocessor terminated; detected suppression of declaration with PL/I %NOPRINT option.

Explanation: The postprocessor determined that %NOPRINT statements were suppressing information needed for processing.

Severity: The processing terminates.

User Response: Remove %NOPRINT statements or use the preprocessor instead.

Pxmmmm340-S

ESS not supported for this version of PL/I. Minimum version required is v3.8.

Explanation: An ESS compile was started with an unsupported version of PL/I.

Severity: The processing terminates.

User Response: Use a supported version of PL/I or remove option ESS(YES).

Pxmmmm341-S

ESS not supported for this version of COBOL. Minimum version required is v5.1.

Explanation: An ESS compile was started with an unsupported version of COBOL.

Severity: The processing terminates.

User Response: Use a supported version of COBOL or remove option ESS(YES).

Pxmmmm344-W 

Listings containing line numbers greater than 999999 not supported.

Explanation: An unsupported COBOL listing in excess of 999,999 lines was detected.
Severity: The language processor continues, but suppresses the DDIO file.
User Response: Ensure that the source program contains a supported number of lines and resubmit the job.