Messages JOB300 through JOB3xx

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

JOB330E taskType memName OID=orderId ODATE odate INVALID RC FROM CTMMEM rc NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error. Non-zero return code from the CTMMEM internal program while reading a calendar.

The job order is not scheduled.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB331E taskType memName OID=orderId ODATE odate READING DATEMEM (CALENDAR) calName FAILED

Explanation: Reading of a calendar failed.

The job order or mission is not scheduled. Depending on whether or not optional wish WM0738 is applied, the program will terminate or continue with the next job.

Corrective Action: Look for prior messages in the IOA Log that explain why this error occurred and make any necessary corrections.

• For a batch daily, correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement), to the values of date-2 (or date-4).
• For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then run the Daily again.

If the previous abend happened after many jobs or missions had been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDREPRQ, CTDPRTRQ, CTDBKPRQ or CTDRSTRQ for missions).

JOB332E taskType memName OID=orderId ODATE odate CALENDAR calName - OPEN FAILED

Explanation: Reading of a calendar failed.

The calName calendar member does not exist in the library described by the DACAL DD statement.

The job order or mission is not scheduled.

Corrective Action: Correct the name of the calName member in the scheduling table, to a name of a valid calendar.

Check whether the DACAL DD statement describes one (and only one) valid Calendar library. Data set concatenation is not supported in this DD statement.

• For a batch daily, correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement), to the values of date-2 (or date-4).
• For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then run the Daily again.

If the previous abend happened after many jobs or missions had been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDREPRQ, CTDPRTRQ, CTDBKPRQ or CTDRSTRQ for missions).

JOB333E taskType memName OID=orderId ODATE odate MISSING DDNAME "DACAL"

Explanation: Reading of a calendar failed.

The DACAL DD statement describes the calendar library.

The job order or mission is not scheduled.

Corrective Action: If this problem occurs during the New Day procedure, correct the JCL and rerun it. Correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement), to the values of date-2 (or date-4).

For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then rerun the Daily again.

If the previous abend happened after many jobs/missions had been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDREPRQ, CTDPRTRQ, CTDBKPRQ or CTDRSTRQ for missions).

JOB334E READING CALENDAR calName FAILED

Explanation: Reading of the specified calendar failed.

The job order or mission is not scheduled.

Corrective Action: Look for prior messages in the IOA Log that explain why the calendar could not be read.

If the error occurred during the New Day procedure or a User daily, correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (DD statement DACHK), to the values of date-2 (or date-4).

For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then rerun the Daily again.

If the previous abend happened after many jobs or missions have been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDMISRQ for missions).

JOB335E taskType memName OID=orderId ODATE odate CALENDAR calName CONTAINS TOO MANY YEARS

Explanation: A calendar contains too many years to be processed.

The job order or mission is not scheduled.

Corrective Action: Delete the oldest years in the calendar. Keeping a history of many years of calendars is unnecessary.

JOB336E taskType memName OID=orderId ODATE odate AN ABEND - abCode OCCURRED WHILE READING CALENDAR calName

Explanation: An abend occurred while reading a calendar.

The job order or mission is not scheduled. The New Day procedure terminates with a condition code of 08.

Corrective Action: Look for the abend code in the relevant IBM literature and respond accordingly.

JOB337E STATISTICAL CALENDAR statCal MUST BE PERIODIC

Explanation: During the job ordering process, the statCal statistical calendar specified in a group or job scheduling definition was found to be in a non-periodic format.

The job order is not scheduled.

Corrective Action: Replace the statCal calendar in the job scheduling definition with a periodic calendar, or modify the statCal calendar to make it periodic.

JOB338E ORDERING DATE odate (YYMMDD) NOT FOUND IN STATISTICAL CALENDAR calendar

Explanation: The Statistical Calendar defined in a job definition does not include the date specified for the Ordering Date of the job. This error usually occurs when the Statistical Calendar does not include the year indicated in the Ordering Date. The ordering process fails.

Corrective Action: Add the definition for the year used in the Ordering Date to the Statistical Calendar.

JOB350S taskType memName OID=orderId ODATE odate INSUFFICIENT MEMORY TO PERFORM func FUNCTION

Explanation: There is insufficient memory to perform the internal New Day procedure function func.

The job order is not scheduled, but the New Day procedure continues to process other job orders.

Corrective Action: For batch, increase REGION size. For TSO, logon again using a larger SIZE parameter.

JOB351I warning_msg

Explanation: This message is a user-defined warning message that is issued by the WRN task type.

Corrective Action: No action is required.

JOB354E taskType memName OID=orderId ODATE odate OPEN OF MEMBER FAILED

Explanation: Open of the warning messages member failed.

This could be due to one of the following:

• The member does not exist in the specified library.
• There is not enough memory to open the member.

The warning order is not activated.

Corrective Action: Do the following:

• Check the validity of the member and library.
• Increase the REGION size allocated for the New Day procedure.

JOB355E taskType memName OID=orderId ODATE odate DSN dsn IN USE (DISP=OLD)

Explanation: The data set described in the MEMLIB parameter is in use.

Another user is holding the data set described by the MEMLIB parameter with DISP set to OLD.

The warning order is skipped.

Corrective Action: Try again later (or try to find the other user).

JOB356E taskType memName OID=orderId ODATE odate DSN dsn - NOT A LIBRARY

Explanation: The data set described in the MEMLIB parameter is not a library (partitioned data set).

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB357E taskType memName OID=orderId ODATE odate DSN dsn - RECFM NOT FIXED

Explanation: The record format of the data set described by the MEMLIB parameter is not fixed.

The warning order is not issued.

Corrective Action: Correct the production parameters table and try again.

JOB358E taskType memName OID=orderId ODATE odate DSN dsn - LRECL NOT 80

Explanation: The record length of the data set described by the MEMLIB parameter is not 80.

The warning order is not issued.

Corrective Action: Correct the production parameters table and try again.

JOB359E taskType memName OID=orderId ODATE odate DSN dsn NOT FOUND

Explanation: The data set described by the MEMLIB parameter is cataloged, but is not found on the disk.

The warning order is not issued.

Corrective Action: Correct the production parameters table or the catalog and try again.

JOB360E taskType memName ODATE odate DSN dsn - DYNAMIC ALLOCATION FAILED

Explanation: Dynamic allocation for the data set described by the MEMLIB parameter failed.

The warning order is not issued.

Corrective Action: Check the validity of the data set name or call BMC Customer Support for assistance.

JOB361E taskType memName OID=orderId ODATE odate INTERNAL ERROR ON func- MISSING PARAMETER. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warn task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB362E taskType memName OID=orderId ODATE odate INTERNAL ERROR ON func- ACT BEFORE INIT. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB363E taskType memName OID=orderId ODATE odate INTERNAL ERROR - INVALID REQUEST FROM CTMLIB. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB364W taskType memName OID=orderId ODATE odate TOO MANY DSNAMES FOR CTMLIB

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB365E taskType memName OID=orderId ODATE odate DSN dsn NOT CATALOGED

Explanation: The data set described by the MEMLIB parameter is not cataloged.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB366E taskType memName OID=orderId ODATE odate UNEXPECTED ERROR ON CTMLIB FUNCTION func. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB367S taskType memName OID=orderId ODATE odate INITIALIZATION OF MAIN LIB FAILED. DDNAME ddName

Explanation: Initialization of main library failed (the ddName DD statement).

Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB368S INSUFFICIENT MEMORY TO PERFORM func FUNCTION

Explanation: Insufficient memory to perform the internal New Day procedure function func.

The job order is not scheduled, but the New Day procedure continues to process other job orders.

Corrective Action: For batch, increase REGION size. For TSO, logon again using a larger SIZE parameter.

JOB369I warning_msg

Explanation: This message is a user defined warning message that is issued by the WRN task type.

Corrective Action: No action is required.

JOB370E taskType memName ODATE odate OPEN OF MEMBER memName DSN dsn FAILED

Explanation: Open of the warning messages member failed.

Possible causes are:

• The member does not exist in the specified library.
• There is insufficient memory to open the member.

The warning order is not activated.

Corrective Action: Do one or both of the following:

• Check the validity of the member and library.
• Increase the New Day procedure REGION size.

JOB371E DSN dsn IN USE (DISP=OLD)

Explanation: Data set described in the MEMLIB parameter is in use.

Another user is holding the data set described by the MEMLIB parameter with DISP set to OLD.

The warning order is skipped.

Corrective Action: Try again later, or find the other user.

JOB372E DSN dsn - NOT A LIBRARY

Explanation: The data set described in the MEMLIB parameter is not a library (partitioned data set).

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB373E DSN dsn - RECFM NOT FIXED

Explanation: The record format of the data set described by the MEMBLIB parameter is not fixed.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB374E DSN dsn - LRECL NOT 80

Explanation: The record length of the data set described by the MEMLIB parameter is not 80.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB375E DSN dsn NOT FOUND

Explanation: The data set described by the MEMLIB parameter is cataloged, but is not found on the disk.

The warning order will not be issued.

Corrective Action: Correct the production parameters table or the catalog and try again.

JOB376E DSN dsn - DYNAMIC ALLOCATION FAILED

Explanation: Dynamic allocation for the data set described by the MEMLIB parameter failed.

The warning order will not be issued.

Corrective Action: Check the validity of the data set name. If necessary, call BMC Customer Support for assistance.

JOB377E INTERNAL ERROR ON func - MISSING PARAMETER. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB378E INTERNAL ERROR ON func - ACT BEFORE INIT. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB379E INTERNAL ERROR - INVALID REQUEST FROM CTMLIB. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB380W TOO MANY DSNAMES FOR CTMLIB

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB381E DSN dsn NOT CATALOGED

Explanation: The data set described by the MEMLIB parameter is not cataloged.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB382E UNEXPECTED ERROR ON CTMLIB FUNCTION func. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB383S INITIALIZATION OF MAIN LIB FAILED. DDNAME ddName

Explanation: Initialization of main library failed (the ddName DD statement).

Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.