Messages REP200 through REP2xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

REP250I REPORT DECOLLATOR STARTED

Explanation: This information message is the normal message when the Control-D monitor internal decollating task is started.

Corrective Action: No action is required.

REP251I DECOLLATION ENDED "OK"

Explanation: This information message is the normal end message of a job decollation.

Corrective Action: No action is required.

REP252I DECOLLATION ENDED "NOT OK"

Explanation: This information message indicates that the decollation of a report/job was not successful.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look at the IOA Log for additional error messages relating to this decollating mission.

REP253E INSUFFICIENT MEMORY TO DECOLLATE THE JOB

Explanation: Insufficient memory to decollate the job.

Corrective Action: Increase the Control-D monitor REGION size, then rerun the decollating mission.

REP254E INTERNAL ERROR - INVALID FORMAT OF AMF RECORD. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: This problem is caused by incompatibility between what can be defined in the Report Decollating screen, and the actual decollating mechanism under the Control-D monitor. There is no need to reformat the Active Missions file. Print the mission definition and send it to your IOA Administrator in order to solve the bug. In the meantime try to bypass the problem by modifying the mission definition (try a different ON WHEN DO combination). If you cannot bypass it, call your IOA Administrator.

REP255E INTERNAL ERROR IN AMF CONVERSION. DECOLLATION ABORTED

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the IOA Log. Call BMC Customer Support for assistance.

REP256E ERROR WHILE READING SYSOUT FROM SPOOL OR FROM CDAM FILES

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the IOA Log. Call BMC Customer Support for assistance.

REP257E INTERNAL ERROR IN RECIPIENT TREE STRUCTURE

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the system log. Call BMC Customer Support for assistance.

REP258E DEFAULT PRIMARY USER NOT FOUND IN TREE OR NO DEFAULT USER SPECIFIED

Explanation: The user (recipient) specified in the DEF USER parameter of the Report Decollating Definition screen is not found in the Recipient Tree or no DEF USER is specified.

A page has been found in the job’s reports which is not identified by a WHEN/DO/USER statement, and no default user is specified.

Control-D assigns the root of the tree as the default, and the mission ends NOTOK.

Corrective Action: Correct the decollation mission, and schedule it again.

REP259E DECOLLATING JOB WITHOUT ANY SUPPLIED DEFAULTS

Explanation: No defaults are supplied in this decollation mission.

A page has been found which is not identified by a WHEN/DO/USER statement. Defaults are required in order to perform the decollation.

The mission ends NOTOK.

Corrective Action: Correct the decollation mission, and schedule it again.

REP25AE VARIABLE LIST ERROR IN FUNCTION func FOR VARIABLE varName

Explanation: An error was detected in the variable list structure.

The variables in this message are:

• func - the variable process function (GET, GETU, PUT, CONC) under which the problem occurred.
• varName - the name of the variable that was being processed when the problem arose.

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Check all the statements in the decollation definition that contain the varName variable, correct them as appropriate, and run this mission again. If the problem persists, contact BMC Customer Support.

REP25BE INVALID PARAMETER parm IN FUNCTION func FOR VARIABLE varName

Explanation: The program that handles the CTDVAR variables received control from Exit CTDX022, but the value of a parameter was invalid.

The variables in this message are:

• parm - the name of the parameter with an invalid value
• func - the variable process function (GET, GETU, PUT, CONC) under which the problem occurred
• varName - the name of the variable that was being processed when the problem arose

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Correct the User Exit CTDX022, and rerun the mission.

REP25CE SYNTAX ERROR IN VARIABLE DEFINITION varDef

Explanation: The definition of the variable in the decollation mission is not correct.

In this message, varDef is the invalid string in the decollation definition.

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Correct the decollation mission definition and rerun the mission.

REP25DE XPATH SYNTAX ERROR FOR VARIABLE varName IN DEFINITION string

Explanation: The DO SET statement in the decollation mission contains an invalid definition of the variable containing the XPATH value.

The variables in this message are:

• varName - the name of the variable that was being processed when the problem arose
• string - the invalid string in the decollation mission definition

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Correct the decollation mission definition and rerun the mission.

REP25EE INVALID TAG WAS DETECTED IN XML REPORT. TAG= string

Explanation: An error was detected in the XML report page.

In this message, string is the invalid string in the XML report.

The status of this decollating mission is set to ENDED NOTOK. Control-D continues processing. All variable values extracted from the page containing the invalid string will be treated as null.

Corrective Action: Correct the XML report, and decollate it again.

REP25FE ERROR IN VARIABLE PROCESS DURING DECOLLATION IN PROGRAM progName

Explanation: This message is issued after one of the following messages:

• REP25AE
• REP25BE
• REP25CE
• REP25DE

In this message, progName is the name of the program that was executing when the problem occurred.

The status of this decollation mission is set to ENDED NOTOK.

Corrective Action: Check the IOA Log for additional error messages relating to this decollation mission.

REP260E ERROR IN ACTIVE USER REPORTS LIST FILE. USER UPDATE FAILED

Explanation: The update to the Active User Report List file failed. Perhaps the Active User Report List file is full or the Index component is corrupted.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Examine relevant CTDU99E and CTD908S messages, take appropriate corrective action, and then rerun the decollating mission. Use the CTDDIG utility to check the integrity of the user file. If the problem persists, contact BMC Customer Support.

REP261E SEVERE ERROR WHILE LOCATING SYSOUT PARAMETERS FROM JES

Explanation: Highlighted, unrollable message.

An internal test of the JES control blocks failed.

Control-D retrieves data set characteristics from the JES2 control blocks. These blocks are release-dependent. To avoid abends, Control-D tests the blocks at the beginning of its process. If the test fails, message REP261E is displayed.

This error is often caused by MSGCLASS for started tasks being set to PURGE or DUMMY. Control-D uses the settings of MSGCLASS for started tasks for test SYSOUT.

Snaps are produced and put in the DADUMP DD statement. Control-D continues to process without retrieving characteristics from the JES Control Blocks.

Corrective Action: Do the following:

1. Ensure that the MSGCLASS output class for the started task (STC) in the JES2PARM member of the SYS1.PARMLIB library is not set to PURGE or DUMMY.
2. If MSGCLASS is set correctly, collect the relevant snaps from the DADUMP DD statement and contact BMC Customer Support.

REP262E ADDITIONAL USER usr NOT FOUND IN TREE

Explanation: The Active User Report List file contains an ADDITIONAL USER that was not found on the Recipient Tree. The ADDITIONAL USER must be defined in the Recipient Tree.

The report will not be directed to that user. Processing continues.

Corrective Action: Add this ADDITIONAL USER to the Recipient Tree, or delete this ADDITIONAL USER from the Active and Permanent User Report List file.

REP263E A "DO NOTOK" HAS BEEN ACTIVATED FOR THIS JOB

Explanation: Informational message - the identifying string for a DO NOTOK statement in the decollating mission was found in the report.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: No action is required.

REP264E NO REPORTS WERE SELECTED FROM SPOOL AND/OR FROM DSNS. CHECK THE "ON" DEFINITIONS

Explanation: No reports matched the decollating mission ON statement parameters.

If the current decollating mission contains the IN QUEUE parameter set to Y, and the job is not processed by another decollating mission, the decollation monitor takes the job ID from the last executed job with the matching job name, and accesses sysout files from the spool using this job ID.

Note:

This job ID appears in the Active Missions screen on the line corresponding to the mission. Note also that for jobs decollated from the spool, the mission always contains the IN QUEUE parameter set to Y.

One or more ON statements are defined in the decollating mission, but no reports were present that matched even one ON statement. Note that the reports can be from the spool and/or from compressed data sets.

Assume that job XYZ produces the following reports:

REPORT CLASSAR1 ATOTAC W

The following parameters are present in the decollating mission for this job:

ON CLASS X DO ....... ON CLASS Y DO .......

When this decollating mission is executed, none of the ON statements will work, since the job did not produce any output on class X or class Y.

If the decollating mission contains ON DSN statements, then the No CDAM data set matched the CDAM retrieval parameters which were supplied.

Note:

Control-D does not select sysouts that have the HOLD=OPER characteristic which can result in the issuing of this message as well.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Do the following:

1. Check the decollating parameters to make sure that the ON statements are correct, and match the expected outputs from the job.
2. If the ON statements are OK, check all the outputs of the job. Verify that all the expected reports were produced on the proper classes, or on the CDAM files.

After the problem has been determined and corrected, rerun the job and/or the decollating mission if necessary.

REP265S ERROR WHILE ALLOCATING A CDAM DATASET

Explanation: Internal Control-D error, or some CDAM error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Check the IOA Log and the system log for additional clarification messages.

REP266E CTDPARM GENOTFND SETTING INVALID FOR CURRENT ENVIRONMENT
REP266E GENERIC DECOLLATION PROCESSING STOPPED

Explanation: The setting of the GENOTFND parameter in CTDPARM is not supported by the MVS/JES configuration of the computer. These two messages are always issued together.

Some options of the GENOTFND parameter in CTDPARM are valid only in certain MVS/JES configurations. For example, JES3 only supports GENOTFND when set to CLASS or DELETE.

The unmatched sysout file remains unchanged.

Corrective Action: Do the following:

1. Manually remove the problematic sysout from the generic class.
2. Correct the GENOTFND parameter in CTDPARM. For a description of the GENOTFND parameter, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.
3. Restart the Control-D monitor after compiling CTDPARM.

REP267I DECOLLATION FROM SPOOL STARTED

Explanation: This information message is the normal start message when a decollating mission starts decollating reports from Spool.

Corrective Action: No action is required.

REP268I DECOLLATION FROM COMPRESSED DSN STARTED

Explanation: This information message is the normal start message when a decollating mission starts decollating reports from compressed data sets.

Corrective Action: No action is required.

REP269I DECOLLATION FROM MQ QUEUE STARTED

Explanation: This information message is the normal start message when a decollating mission begins decollating reports from the IBM WebSphere MQ queue.

Corrective Action: No action is required.

REP269S ERROR WHILE DECOLLATING A GENERIC MISSION

Explanation: The attempt to read sysout from the spool failed.

Control-D has started to read sysout from the spool but a nonzero return code was received from JES.

Control-D continues processing.

Corrective Action: Please check whether JES is up or down.

REP26AE MISSION ABENDED syscode usrcode

Explanation: Highlighted, unrollable message.

The decollation mission abended with either the system code syscode, or the user code usrcode, or both.

The decollation mission finishes NOTOK. Control-D tries to process other missions.

Corrective Action: If Control-D cannot process other missions, stop and restart the Control-D monitor. Save the job log of the Control-D decollation monitors and the output referenced by the IOADUMP DD statement of the decollation monitor which processed the problematic mission. Contact BMC Support.

REP26BE SUBSYSTEM REQUEST FAILED FOR JOB jobName. RC15=rc, SSOBRETN=ssobretn_rc

Explanation: A “sysout processing” request caused an unexpected return code to be received from JES.

JES was unable to satisfy the request.

The variables in this message are:

• jobName - the name of the job in which the request failed
• rc - the code returned in register 15
• ssobretn_rc - the contents of the SSOBRETN field of the request block

Corrective Action: Verify that JES is active and functions normally. If JES is functioning normally, save all sysouts of this execution of the Control-D monitor and contact BMC Customer Support. Request RESTORE of the problematic report again.

REP26DW variableTextMsg

Explanation: A text message is issued from the DAL transformer while a report is being decollated with transformation. The text, which may be information, a warning, or an error message, is directly related to the event that produced it, and provides specific information about that event.

The action that the system implements is included in the message text.

Corrective Action: The required user response is included in the message text.

Note:

For documentation of the following transformer messages listed under the current message, see, “Control-D Transformation Messages”:

• BMCDAL0009E TCL.Size : Missing resource resourceName (Type: resourceType)
• BMCDAL0614E TransformObject.ConvertObject: ConvObject_Create Create resource failed: resourceName (Type resourceType), rc= returnCode
• BMCDAL0678W Xerox warning cdpXerox returnCode : messageText
• BMCDAL0679E Xerox error cdpXerox returnCode : messageText

REP26EE ERROR IN DAL TRANSFORMER

Explanation: The DAL transformer found an error while a report was being decollated with transformation.

The decollating mission ends NOTOK.

Corrective Action: Examine the IOA Log for REP26DW messages relating to this decollating mission.

REP26FE APPROVAL approval NOT FOUND IN APPROVAL TREE

Explanation: The Approval name specified in the DO APPROV statement of the Report Decollation Definition screen is not found in the Approval Tree. The mission ends NOTOK.

Corrective Action: Correct the decollation mission and reschedule the mission.

REP26GW MASK RULER Ruler_name NOT FOUND IN PERMANENT FILE FOR RECIPIENT

Explanation: The Mask Ruler Ruler_name specified in the DO MASKRUL statement of the Report Decollation Definition is not found in the Permanent User File.

The information about the report is provided in message CTDI0CI, which follows this message.

The mission ends OK WITH ERRORS.

Corrective Action: Correct the decollation mission or create the Mask Ruler and reschedule the mission.

REP26HE GENERIC MISSION ABENDED SXXX UXXXX. GENERIC DECOLLATION PROCESSING STOPPED

Explanation: Highlighted, unrollable message.

The generic decollation mission abended with the system code or the user code or both these codes displayed in this message. The decollation mission finishes NOTOK. CONTROL-D deactivates the Generic decollation process.

Corrective Action: Save the job log of the CONTROL-D decollation monitors and the output referenced by DD statement IOADUMP of the decollation monitor that processed the problematic mission. Call BMC Software Customer Support.

REP270E SYSOUT PURGED. GENERIC DECOLLATING MISSION NOT FOUND FOR THE JOB

Explanation: Control-D found a non-held output on one of the Classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission (on the Active Missions file) which matches the job name. If a match is not found, the sysout is processed according to the Control-D installation the GENOTFND parameter. For more information, see the INCONTROL for z/OS Administrator Guide.

Control-D continues processing.

Corrective Action: No action is required.

REP271I GENERIC JOB DECOLLATION IS INACTIVE

Explanation: This information message indicates that Generic Processing is not active. The reason the message is issued depends in which of the following formats the message is issued.

• regular, rollable message - indicates that the corresponding Control-D monitor does not perform the Generic Processing. The Control-D monitor issues the message when it is started and after new day processing.
• highlighted, unrollable message - indicates that a job is waiting to be decollated in one of the Generic classes, but Generic Processing is not active. This message will appear every 10 minutes, until Generic Processing is activated.

Control-D continues processing, but no Generic Processing will be done.

Corrective Action: Use the following guidelines to resolve the problem:

• If you have Generic Missions that CTDNDAY processing should order , ensure that the GENLIST member contains the library and table name for your Generic Missions
• If you have a Library and table names in the GENLIST member, ensure that the MEMBERS really exist in the library. Also verify that the library is the correct name.
• Check to see if CTDNDAY processing had an error during the ordering of GENLIST. If an error occurred the deactivation of Generic Processing is automatic.
• Check to see if someone issued the STOPGEN command.

Issue the following command, to activate Generic Processing:

F CONTROLD,STARTGEN

The application will respond by displaying the following message:

CTD139I GENERIC JOB DECOLLATION IS ACTIVE ON CLASSES (claslist)

To verify your classes, check the GENCLAS= parameter in the CTDPARM member.

Note:

If there are NO Generic Missions being ordered during the CTDNDAY processing, you need to manually activate Generic Processing if you are manually Forcing/Ordering Generic Missions.

For more information on activating and deactivating generic processing, see the INCONTROL for z/OS Administrator Guide.

REP272W SYSOUT REMOVED FROM QUEUE
REP272I GENERIC DECOLLATING MISSION NOT FOUND FOR JOB jobName

Explanation: Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout. These two messages are always issued together.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission (on the Active Missions file) which matches the job name. If a match is not found, the sysout is processed according to the GENOTFND Control-D installation parameter. Refer to the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

Control-D continues processing.

Corrective Action: Check to see if the Generic decollating mission for this job should be on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

REP273I SYSOUT CLASS CHANGED FROM CLASS x TO ESCAPE CLASS y

Explanation: This information message indicates that Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission on the Active Missions file that matches the job name. If a match is not found under JES3, Control-D changes the sysout’s class to an Escape Class as specified in the GENOTFND Control-D installation parameter and the output remains on the spool. Refer to the INCONTROL for z/OS Administrator Guide.

Control-D continues processing.

Corrective Action: Check to see if the Generic decollating mission for this job should be Active on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

REP274W MQ DECOLLATING MISSION NOT FOUND FOR THE MESSAGE FROM MQ QUEUE mqQueueName

Explanation: There is no appropriated mission with matched selection parameters for this message from the IBM WebSphere MQ queue.

This message will be moved to the IBM WebSphere MQ escape queue. The name of the escape queue must be defined in the CTDMQPRM parameter of the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

REP275E ERROR WHILE DECOLLATING FROM MQ mqQueueName

Explanation: The decollation was started, but a nonzero code was returned.

Control-D continues processing.

Corrective Action: Check any additional messages received during this IBM WebSphere MQ decollation.

REP276I MESSAGE MOVED TO MQ ESCAPE QUEUE queueName

Explanation: This information message indicates that the message was moved to the queueName queue that was defined in the CTDMQPRM parameter of the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

REP277W THE DATA LENGTH IS ZERO IN THE MESSAGE FROM MQ QUEUE queueName

Explanation: The message from the IBM WebSphere MQ queue cannot be decollated because the message data length is zero. The message will be moved to the IBM WebSphere MQ escape queue.

The name of the escape queue must be defined with the CTDMQPRM parameter in the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

REP278E SYSOUT ALLOCATION FAILED, JobName,JobId,DDName, RC=rc, ERROR=rsn

Explanation: An error was encountered when Control-D tried to allocate a sysout for decollation.

The variables in this message are:

• jobName - the name of the job with the problematic sysout
• jobId - the job ID of the job with the problematic sysout
• DDName - the name of the DD statement with the problematic sysout
• rc - dynamic allocation return code
• rsn - dynamic allocation reason code

Corrective Action: Try to correct the sysout. If the problem persists, contact your system programmer for assistance. Keep all sysouts from this execution of the Control-D monitor, and contact BMC Customer Support.

REP279E MULTIPLE APPROVAL PROCESS WAS DEFINED INCORRECTLY FOR REPORT rename

Explanation: This message can be issue in the following conditions:

• Control-D has detected that a report that was defined for multiple approval processing (MULTI=S) was not created. The status of the related reports created from the same SYSOUT is set to Candidate.
• A report that was defined for multiple approval processing (MULTI=S) refers to more than one CDAM. Control-D does not expand multiple approval processing on secondary CDAMs. Reports referring to these CDAMs cannot be approved.

Corrective Action: Check the decollation mission or the original report to assure that all reports and corresponding approval components have been created correctly.

REP27AE ERROR ERROR IN APPROVAL PROCESSING

Explanation: This message is issued after the REP279E or REP26FE message.The status of this decollation mission is set to ENDED NOTOK.

Corrective Action: Check the IOA log for additional error messages relating to this decollation mission.

REP27BE APPROVAL aprvname HAS INCORRECT APPROVAL TREE DEFINITION

Explanation: The aprvname Approval name is defined incorrectly in the Approval Tree.

This message is issued if the WDN051 Optional wish is applied (APPLY=YES) in the following conditions:

• The aprvname Approval name has no authorized users and has no child items (incorrect Parallel Approval).
• The aprvname Approval name has child items that have no authorized users.
• The aprvname Approval name for a Parallel Approval process has more than 15 child items.

Corrective Action: Check the Approval Tree and adjust the relevant Approval items.

REP27CW jobId,jobName,ddName FROM numSpool LINES ON SPOOL
REP27CI numRead LINES ARE READ

Explanation: During decollation of SYSOUT, Control-D checks the number of read lines and the number of lines in SSOB (SSSOLNCT or SSS2LNCT). If the number of lines read from the spool is equal to or greater than the number from SSOB, Control-D decollates the SYSOUT. These two messages are issued if the number of read lines is less than the number in SSOB, as Control-D considers the SYSOUT corrupted due to lost information. SYSOUT remains in the spool.

The variables in these messages are:

• jobName - the name of the job with the sysout in which the mismatch occurred
• jobId - the job ID of the job with the sysout in which the mismatch occurred
• ddName - the name of the DD statement with the sysout in which the mismatch occurred
• numSpool - the number of lines of sysout on the spool
• numRead - the number of lines of sysout read from the spool

The decollation mission finishes NOTOK.

Corrective Action: Try to correct the sysout. If it is not possible to correct the sysout, and you want Control-D to process such corrupted sysouts, temporarily specify APPLY=Y for the optional wish WD3597. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

Note: BMC recommends not to specify APPLY=Y for the optional wish WD3597 as a permanent setting.

REP27EW jobId,jobName,ddName FROM numRead LINES READ FROM SPOOL
REP27EI numLines LINES IN numPages PAGES PASSED TO CDAM

Explanation: The number of lines of sysout read from the spool is not the same as the number of lines of sysout written to CDAM. These two messages are always issued together.

The variables in these messages are:

• jobName - the name of the job with the sysout in which the mismatch occurred
• jobId - the job ID of the job with the sysout in which the mismatch occurred
• ddName - the name of the DD statement with the sysout in which the mismatch occurred
• numRead - the number of lines of sysout read from the spool
• numLines - the number of lines of sysout written to CDAM
• numPages - the number of pages of sysout written to CDAM

The Control-D monitor terminates with the user code U027.

Corrective Action: If there is an urgent reason to temporarily bypass the U027 abend, specify APPLY=Y for the optional wish WD3597. (Note that some lines from the spool might be lost.) Keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

Note: BMC recommends not to specify APPLY=Y for the optional wish WD3597 as a permanent setting.

REP27FI jobId,jobName,ddName SYSOUT IS HELD IN GENERIC CLASS clss

Explanation: The sysout of the identified job cannot be decollated by a generic decollation mission. The reason is an error identified in a previous message.

The variables in this message are:

• jobName - the name of the job with the problematic sysout
• jobId - the job ID of the job with the problematic sysout
• ddName - the name of the DD statement with the problematic sysout
• clss - the spool class of the sysout

Processing continues, but the status of the sysout is set to HELD.

Corrective Action: Examine the log for the previous message that identifies the error, and proceed according to the User Response for that message.

REP27GE jobId,jobName,ddName JES I/O ERROR RSN rsn FOR SYSOUT CLASS clss

Explanation: A JES I/O error occurred during the reading of sysout from the spool.

The variables in this message are:

• jobName - the name of the job with the sysout that was being read when the mismatch occurred
• jobId - the job ID of the job with the sysout that was being read when the mismatch occurred
• ddName - the name of the DD statement with the sysout that was being read when the mismatch occurred
• rsn - the reason code from the FDBK field of JES
• clss - the spool class of the sysout

The decollation mission finishes NOTOK.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

REP27HI ZIIP ISN'T USED

Explanation: This information message indicates that the zIIP processor is not being used by the Control-D decollation monitor, as it is defined in the CTDPARM.

Additional messages identify the specific reason why the zIIP processor is not being used.

Corrective Action: Check the IOA log file and the system log for the reason. Contact your system programmer for assistance if needed.

REP27II ZIIP IS USED

Explanation: This information message indicates that the zIIP processor is being used by the Control-D decollation monitor.

Corrective Action: No action is required.

REP27JE jobName, jobId, ddName OPEN ERROR RS rs ERFLG err FOR SYSOUT CLASS clss

Explanation: An error occurred while attempting to open a SYSOUT for decollation.

The variables in this message are:

• jobName - the name of the job with the sysout that caused the problem
• jobId - the job ID of the job with the sysout that caused the problem
• ddName - the name of the DD statement with the sysout that caused the problem
• rc - the return code from the OPEN
• err - the reason code from the ACBERFLG field
• clss - the spool class of the sysout

The decollation mission finishes NOTOK. The REP27FI message, which follows, indicates that the status of the problematic SYSOUT is set to HELD.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.