Messages BSD300 through BSD3xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

BSD310I IOACPRM M2S=ctm2sbs

Explanation: This information message provides you with the name of the CTM2SBS file.

Corrective Action: No action is required.

BSD311I SMFID=smfid SYSTEM=system_name S2M=sbs2ctm

Explanation: This information message provides you with the SMFID, the system name, and the SBS2CTM file name.

Corrective Action: No action is required.

BSD314I ADDING SMFID smfid WAS SUCCESSFUL

Explanation: This information message indicates that a new SMFID (smfid) was added successfully to the CMEM monitor, to the M2S subsystem file, by the FORMSUB3 job.

Corrective Action: To make the definition active, stop and restart the Control-M monitor and the Control-O or CMEM monitor on the system with the SMFID.

BSD315I {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS STARTED

Explanation: This information message indicates that the FORMSUB1 and FORMSUB2 utilities, which allocate and format Console Subsystem communications files, have started.

Corrective Action: No action is required.

BSD316I {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS ENDED

Explanation: This information message indicates that the FORMSUB1 and FORMSUB2 utilities, which allocate and format Console Subsystem communications files, have ended normally.

Corrective Action: No action is required.

BSD317S {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS FAILED

Explanation: The FORMSUB1 or the FORMSUB2 utility failed.

Corrective Action: Look for a previous error message which describes the cause of the error.

BSD318S OPEN OF DDNAME ddName FAILED

Explanation: Open of the ddName DD statement failed.

Possible causes are:

• The ddName DD statement is missing.
• The ddName DD statement does not define a valid communication file.

Corrective Action: Correct the JCL of the formatting job.

BSD319S I/O ERROR OCCURRED WHILE BUILDING THE SUBSYSTEM COMMUNICATION DATASETS

Explanation: An I/O error occurred while the FORMSUB1 or the FORMSUB2 utility was formatting a subsystem communication file.

Possible causes are:

• The utility loaded old and incorrect IOACPRM installation parameters.
• The JCL references an invalid data set.
• The file size defined in the IOACPRM parameters member is different from the size that was defined in the JCL.

Corrective Action: Check the JCL of the formatting job, and the location and content of the IOACPRM member.

BSD325S SMFID smfid IS NOT DEFINED IN IOA INSTALLATION PARAMETERS

Explanation: The FORMSUB1 or the FORMSUB2 utility is running under a CPU that was not defined in the IOACPRM parameters member.

Possible causes are:

• The CPU in which the utility was run was not defined in IOACPRM.
• The utility loaded an incorrect copy of the IOACPRM member.
• The computer in which the utility was run is a multi-CPU computer, and the SID parameter in the SMFPRM xx member in SYS1.PARMLIB does not define all of the CPUs correctly.

Corrective Action: Do the following:

• Check what CPUs were defined in IOACPRM.
• Check where the IOACPRM member was placed.
• If the IOACPRM definition seems to be correct, check the SMFID that was defined in SYS1.PARMLIB.
• In a multi-CPU computer, issue the MVS command D M=CPU from the console to get a listing of all CPU serial numbers, and compare them with the PARMLIB definitions.

BSD326E MISSING/INVALID SUBSYSTEM PARAMETERS IN IOACPRM

Explanation: The FORMSUB1 or the FORMSUB2 utility encountered one or more subsystem-related parameters in the IOACPRM member that were defined incorrectly or were not defined at all.

Corrective Action: Check the following parameter definitions in the IOACPRM member, and correct them if needed:

• SUBSYS
• CTM2SBS
• CPUS.