Messages BMC9800 through BMC9899 (ULTRAOPT and MainView for VTAM)

IDCAMS ERROR

Explanation: An error was detected during the processing of an IDCAMS function. The job is terminated with a user 4040 abend.

User response: Review the SYSPRINT output for the cause of the error and resubmit the job.

AUTHLIB DD statement missing

Explanation: An AUTHLIB DD statement was not found in the JCL. The job is terminated with a user 4040 abend.

User response: Insert an AUTHLIB DD statement and resubmit the job.

parm parameter missing

Explanation: The SYSID or SUFFIX PARM is invalid or missing. The job is terminated with a user 4040 abend.

User response: If the job step executes the program xxxBAMS, code a PARM of SYSID= sysid. xxx is the product code.

Open/Close error RC= rr FDBK= ff

Explanation: An open/close error was detected while initializing the VSAM Options file. rr is the return code, and ff is the feedback code. The job is terminated with a user 4040 abend.

User response: To determine the cause of the error, see the IBM VSAM Programmer’s Guide.

RPL ERROR RC= rr FDBK= ff

Explanation: An RPL error was detected while initializing the VSAM Options file. rr is the return code, and ff is the feedback code. The job is terminated with a user 4040 abend.

User response: To determine the cause of the error, see the IBM VSAM Programmer’s Guide.

Invalid delete found

Explanation: A request was made to delete a VSAM file, but the VSAM file was invalid or missing. The job is terminated with a user 4040 abend.

User response: Check the VSAM file name. If the name is correct, notify BMC Customer Support for programming support.

Cluster name missing

Explanation: A request was made to define a VSAM file, but the VSAM file was invalid or missing. The job is terminated with a user 4040 abend.

User response: Check the VSAM file name. If the name is correct, notify BMC Customer Support for programming support.

DDNAME name missing

Explanation: A request was made to define a VSAM file, but the FILE statement was missing in the SYSIN. The job is terminated with a user 4040 abend.

User response: Check the SYSIN for the FILE operand. The operand is used to define the DDNAME that will be associated with the VSAM file.

FILE filename already exists

Explanation: A new VSAM file is being defined, but filename already exists. The old data set name is replaced by the new data set name. Message BMC9809I follows this message and displays the old data set name. The job is completed with return code 0.

User response: No action is required.

old data set name

Explanation: This message always follows message BMC9808I. It displays the old data set name that was replaced. The job is completed with return code 0.

User response: No action is required.

tablename table saved

Explanation: The table tablename was saved into the APF-authorized library that is pointed to by the AUTHLIB DD statement. The job is completed with return code 0.

User response: No action is required.

TABLE tablename DELETED

Explanation: The table tablename was deleted in the APF-authorized library that is pointed to by the AUTHLIB DD statement. The table was deleted because no entries were found in the FDT. The job is completed with return code 4.

User response: No action is required.

error message

Explanation: An allocation error occurred. The x in the message number indicates the severity of the problem. The job is terminated with a user 4040 abend.

User response: For information about why the error occurred, see the message text.

error message

Explanation: An error occurred during the linking of a load module. The job is terminated with a user 4040 abend.

User response: For information about why the error occurred, see the message text.

xxxMSG program is unable to execute

Explanation: The xxx product tried to load the module xxxMSG, and the LOAD failed. The product is not started.

User response: Ensure that the xxxMSG module is in a library that is in the subsystem STEPLIB, JOBLIB, or LINKLIST concatenation.