Previous Topic: CAW4 Messages

Next Topic: GNT Messages

CDYF Messages

List of CDYF Messages

The CAISDI/elmds component produces the messages in this chapter.

For CDYF messages, if unique appears in the message, it is a unique number associated with the unit of work. If tracing is active, trace messages display the unique number so all messages for that unit of work can be identified.

Messages CDYF901I through CDYF989I are only issued when tracing has been requested. Those messages are not defined here.

The Event Trigger Utility CDYFELS1 (for els support) issues the messages that start with CDYF8nnn.

CDYF001I

CAISDI/elmds Initialized

Reason:

CAISDI/elmds has completed initialization.

Action:

No action necessary.

CDYF002I

CAISDI/elmds Starting termination

Reason:

CAISDI/elmds has been requested to terminate.

Action:

No action necessary.

CDYF003I

CAISDI/elmds Terminated

Reason:

CAISDI/elmds has been completed its termination phase.

Action:

No action necessary.

CDYF004E

Unable to establish ESTAEX - R15=rc

Reason:

CAISDI/elmds was unable to establish its main recovery routine.

rc is the R15 contents from the ESTAEX macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF005E

LOAD for message table lmod failed, R15=rc R01=code

Reason:

CAISDI/elmds was unable to load the specified module to build the internal message table.

lmod is the name of the module.

rc is the R15 contents from the LOAD macro (in hex).

code is the R01 contents from the LOAD macro (in hex).

Action:

CAISDI/elmds terminates. Verify that the module is available (Link-List or STEPLIB).

CDYF006E

Error attaching lmod, R15=rc

Reason:

CAISDI/elmds was unable to attach the specified module.

lmod is the name of the module.

rc is the R15 contents from the ATTACHX macro (in hex).

Action:

CAISDI/elmds terminates. Verify that the module is available (Link-List or STEPLIB).

CDYF007E

Error initializing subtask name

Reason:

CAISDI/elmds encountered an error initializing an attached subtask.

name is the name of the subtask.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF008E

LOG handler unexpectedly terminated, CDYFLOG output terminated

Reason:

The CAISDI/elmds output handler encountered an error.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF009E

Already active, ENQ error rc

Reason:

CAISDI/elmds encountered an ENQ error. An ENQ is issues to verify that only one instance is active on an LPAR.

rc is the return code set by the ENQ macro (in hex).

Action:

CAISDI/elmds terminates. This message indicates another copy is already active. Only one instance of CAISDI/elmds can be active on an LPAR. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF010I

Active request, will wait up to 60 seconds

Reason:

CAISDI/elmds detected activity during its termination phase.

Action:

No action necessary.

CDYF011E

NameToken error: function name R15=rc

Reason:

CAISDI/elmds encountered an error querying, defining, or deleting a name token.

function is the NameToken function.

name is the name of the name token.

rc is the R15 contents from the specified function (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF012E

STORAGE OBTAIN error for ICT, R15=rc

Reason:

CAISDI/elmds encountered a STORAGE OBTAIN error for the ICT control block located in CSA.

rc is the R15 contents from the STORAGE macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF013E

STORAGE OBTAIN error for API, R15=rc

Reason:

CAISDI/elmds encountered a STORAGE OBTAIN error for the API module that is loaded in CSA.

rc is the R15 contents from the STORAGE macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF014E

BLDL error for lmod R15=rc

Reason:

CAISDI/elmds encountered a BLDL error for the specified load module.

lmod is the name of the specified module.

rc is the R15 contents from the BLDL macro (in hex).

Action:

CAISDI/elmds terminates. Insure the module is available (Link-List or STEPLIB). If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF015E

BLDL indicated lmod in private library

Reason:

CAISDI/elmds determined the specified module resides in a private library.

lmod is the name of the specified module.

Action:

CAISDI/elmds terminates. Verify that the module is available in the Link-List or STEPLIB. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF016E

ETCON error R15=rc

Reason:

CAISDI/elmds encountered an ETCON macro error while trying to establish the PC environment.

rc is the R15 contents from the ETCON macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF017E

LOAD failed for lmod failed, R15=rc R01=code

Reason:

CAISDI/elmds was unable to load the specified module.

lmod is the name of the module.

rc is the R15 contents from the LOAD macro (in hex).

code is the R01 contents from the LOAD macro (in hex).

Action:

CAISDI/elmds terminates. Verify that the module is available (Link-List or STEPLIB).

CDYF018I

GETDSAB failed R15=rc R00=reason

Reason:

The GETDSAB macro returned an error (used to set values for any spun output).

rc is the R15 contents from the GETDSAB macro (in hex).

reason is the R00 contents from the GETDSAB macro (in hex).

Action:

Processing continues. Defaults are set: The DEST, FORM and WRITER are set to blanks and the CLASS is set to “*” (relevant if the output is spun).

CDYF019E

Error obtaining latches R15=rc

Reason:

The routine to obtain latches (ISGLCRT) returned an error.

rc is the R15 contents from ISGLCRT (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF020E

STORAGE OBTAIN error for LSI, R15=rc

Reason:

CAISDI/elmds encountered a STORAGE OBTAIN error for storage to identify the Latch Set.

rc is the R15 contents from the STORAGE macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF021E

Error identifying latches R15=rc

Reason:

The routine to identify a latch set (ISGLID) returned an error.

rc is the R15 contents from ISGLID (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF022E

Event manager task unexpectedly terminated

Reason:

CAISDI/elmds detected that the event manager task unexpectedly terminated.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF023E

Timer task unexpectedly terminated

Reason:

CAISDI/elmds detected that the timer manager task unexpectedly terminated.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF024E

ENFREQ error: function R15=rc

Reason:

CAISDI/elmds detected an error from the ENFREQ macro.

rc is the R15 contents from ENFREQ (in hex).

Action:

If the function is LISTEN, then CAISDI/elmds terminates. Collect relevant messages and contact CA Support. If the function is DELETE, the error occurred during termination; termination continues.

CDYF025E

Event handler task unexpectedly terminated

Reason:

CAISDI/elmds detected that the event handler task (attached by the event manager) unexpectedly terminated.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF030E

Abend processing message file

Reason:

CAISDI/elmds abended initializing the internal message file.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF031E

Error opening message file CDYFMSGS

Reason:

CAISDI/elmds was unable to open the external message file allocated to DDNAME CDYFMSGS.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF032E

Message file must be FIXED or VARIABLE

Reason:

The record format (DCB RECFM) of the external message file allocated to DDNAME CDYFMSGS must be F, FB, V, or VB.

Action:

CAISDI/elmds terminates. Verify that the DCB RECFM is one of the allowed formats.

CDYF033E

Message file logical record length too big

Reason:

The logical record length (DCB LRECL) of external message file allocated to DDNAME CDYFMSGS cannot exceed 256. For fixed files, the LRECL cannot exceed 256; for variable files the LRECL cannot exceed 260 (4-byte record descriptor word).

Action:

CAISDI/elmds terminates. Verify that the DCB LRECL is within bounds.

CDYF034E

MSGID length error on line linenum

Reason:

The first token in a message definition in the external message file allocated to DDNAME CDYFMSGS must be a 7-byte message ID. CAISDI/elmds detected a noncomment line where the first token was not 7 bytes.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF035E

Missing WTO or NOWTO on line linenum

Reason:

The second token in a message definition in the external message file allocated to DDNAME CDYFMSGS must be WTO or NOWTO. CAISDI/elmds detected a noncomment line where the second token was missing.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF036E

Second token on line linenum must be WTO or NOWTO

Reason:

The second token in a message definition in the external message file allocated to DDNAME CDYFMSGS must be WTO or NOWTO. CAISDI/elmds detected a noncomment line where the second token was not valid.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF037E

Missing message text on line linenum

Reason:

Message text is required after the second token in a message definition in the external message file allocated to DDNAME CDYFMSGS (no message ID only messages). CAISDI/elmds detected a noncomment line that was missing text.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF038E

Message id msgid on line linenum not found

Reason:

The message id in a message definition in the external message file allocated to DDNAME CDYFMSGS was not found in the internal message file.

msgid is the message id (first token online) from the external message file.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF039E

Message id msgid on line linenum cannot be overridden

Reason:

The message ID in a message definition in the external message file allocated to DDNAME CDYFMSGS matches a message ID in the internal message file. Therefore, the message definition cannot be overridden.

msgid is the message id (first token online) from the external message file.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF040E

Text for message id msgid on line linenum too long

Reason:

The message text for the message ID in the message definition in the external message file allocated to DDNAME CDYFMSGS is too long. The maximum length of the message text is documented in CDYFMSGS.

msgid is the message id (first token online) from the external message file.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF041E

Duplicate message id msgid on line linenum

Reason:

The message ID in the message definition in the external message file allocated to DDNAME CDYFMSGS is a duplicate of a previously processed message.

msgid is the message id (first token online) from the external message file.

linenum is the line number in the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF042E

Missing message id msgid

Reason:

The specified message ID is defined in the internal message file indicating the text must be provided. However, the message ID did not appear in any message in the external message file allocated to DDNAME CDYFMSGS.

msgid is the message id (first token online) from the external message file.

Action:

CAISDI/elmds terminates. Correct the message definition.

CDYF050E

dbg - abend in pgm pgmaddr PSW psw_h psw_l CODE cmpc CRC crc R15 gr15

Reason:

CAISDI/elmds detected an abend.

dbg is the recovery routine that was given control.

pgm is the program that was in control.

pgmaddr is the address of pgm.

PSWpsw_h and psw_l is the PSW from SDWAEC1. The 8-byte PSW is displayed (in hex) in the two 4-byte fields psw_h and psw_l.

cmpc is the SDWACMPD (in hex).

crc is the SDWACRC (in hex).

gr15 is SDWAGR15 (in hex).

Action:

CAISDI/elmds continues.

CDYF051I

PASN pasn SASN sasn HASN hasn SDWAFMID asid

Reason:

This message generally follows CDYF050E and provides information about the abend.

pasn is the PASN (ASID of the Primary Address Space) at time of error.

sasn is the SASN (ASID of the Secondary Address Space) at time of error.

hasn is the HASN (ASID of the HOME Address Space) at time of error.

asid is the SDWAFMID field from the SDWA.

Action:

CAISDI/elmds continues.

CDYF052I

range reg1/areg1 reg2/areg2 reg3/areg3 reg4/areg4

Reason:

This message generally follows CDYF050E and provides information about the abend.

range is the literal string R00-R03, R04-R07, R08-R11, or R12-R15. The range indicates the registers and access registers that follow in order.

reg1 is the first general register in the range. Likewise reg2 is the second, reg3 is the third and reg4 is the fourth.

areg1 is the first access register in the range. Likewise areg2 is the second, areg3 is the third and areg4 is the fourth.

Action:

CAISDI/elmds continues.

CDYF053I

SDWAEC2 psw_h psw_l

Reason:

This message generally follows CDYF050E and provides information about the abend. This message is displayed when the error occurred on an RB other than the one that established the recovery environment. For example, if an error occurred in POST code, SDWAEC1 in CDYF050E and the registers in CDYF052I are from the POST code. SDWAEC2 generally points to the code that issued the POST.

psw is the PSW from SDWAEC2. The 8-byte PSW is displayed (in hex) in the two 4-byte fields psw_h and psw_l.

Action:

CAISDI/elmds continues.

CDYF054I

range reg1 reg2 reg3 reg4

Reason:

This message generally follows CDYF053I and provides information about the abend. This message displays the registers that are related with the PSW displayed in CDYF053I.

range is the literal string R00-R03, R04-R07, R08-R11, or R12-R15. This range indicates the registers and access registers that follow in order.

reg1 is the first general register in the range. Likewise reg2 is the second, reg3 is the third and reg4 is the fourth.

Action:

CAISDI/elmds continues.

CDYF055E

dbg - abend in pgm recovery routine

Reason:

CAIDSI/elmds detected and abend in the recovery routine while processing and abend.

dbg is the recovery routine that was in control.

pgm is the program that was in control when the recovery routine was first entered.

Action:

CAISDI/elmds continues.

CDYF056I

rcvy - recovery routine entered for pgm

Reason:

A program had requested that a local recovery routine be given control during abend processing. An abend has occurred and the local recovery routine has been entered.

rcvy is the local recovery routine that is in control.

pgm is the program that requested local recovery.

Action:

CAISDI/elmds continues.

CDYF057I

SVCDUMP R15=rc ECB_RC=ecbrc

Reason:

A suspend type SVCDUMP has been requested and has completed (either successfully or in error).

rc is the R15 from the SDUMPX macro.

ecbrc is return code set then ECB after the WAIT.

Action:

CAISDI/elmds continues.

CDYF060I

TRACE trc SYSUDUMP sysu SVCDUMP svcd SPIN stat class class

Reason:

An operator QUERY command was entered.

trc is ON or OFF.

sysu is ON or OFF.

svcd is ON or OFF.

stat is OFF or the decimal spin value.

class is spin class.

Action:

CAISDI/elmds continues.

CDYF061I

No MED SERVERs defined

Reason:

An operator MEDDISPLAY command was entered but there are no servers defined in the MEDPARMS.

Action:

CAISDI/elmds continues.

CDYF062I

MED SERVER server not found

Reason:

An operator MEDENABLE or MEDDISABLE command was entered for server but that server was not found.

Action:

CAISDI/elmds continues.

CDYF063I

MED SERVER server is state

Reason:

An operator MEDDISPLAY command was entered.

server is the name of the MED server from the MEDPARMS.

state is ENABLED or DISABLED and is state of the server.

Action:

CAISDI/elmds continues.

CDYF064I

MED SERVER server set to state

Reason:

An operator MEDENABLE or MEDDISABLE command was entered.

server is the name of the MED server from the MEDPARMS.

state is ENABLED or DISABLED and is state of the server.

Action:

CAISDI/elmds continues.

CDYF065I

No ELS PRODUCTs defined

Reason:

An operator ELSDISPLAY command was entered but there are no ELS products defined in ELSSTART.

Action:

CAISDI/elmds continues.

CDYF066I

ELS PRODUCT product not found

Reason:

An operator ELSENABLE or ELSDISABLE command was entered for product but that product was not found.

Action:

CAISDI/elmds continues.

CDYF067I

ELS PRODUCT product is state

Reason:

An operator ELSDISPLAY command was entered.

product is the name of the ELS product from ELSSTART.

state is ENABLED or DISABLED and is state of the product.

Action:

CAISDI/elmds continues.

CDYF068I

ELS PRODUCT product set to state

Reason:

An operator ELSENABLE or ELSDISABLE command was entered.

product is the name of the ELS product from ELSSTART.

state is ENABLED or DISABLED and is state of the product.

Action:

CAISDI/elmds continues.

CDYF069I

LOGREC interface is state

Reason:

An operator LOGREC DISPLAY command was entered. This message pertains to the creation of tickets based on listening for IBM LOGREC events.

state is ENABLED or DISABLED.

Action:

CAISDI/elmds continues.

CDYF070I

TIMEOUT value

Reason:

An operator QUERY command was entered. The TIMEOUT command is used to set the TIMEOUT value.

value is the decimal number of seconds which overrides any timeout value defined through MEDPARMS or ELSSTART. This value is used as the CAICCI timeout value for communicating with the CAISDI/soap Server.

Action:

CAISDI/elmds continues.

CDYF100I

text

Reason:

This message echoes a line from the CDYFCNFG file.

text is the configuration statement.

Action:

CAISDI/elmds continues.

CDYF101E

Abend processing configuration file CDYFCNFG

Reason:

CAISDI/elmds detected an abend processing the configuration file.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF102E

Error opening configuration file CDYFCNFG

Reason:

CAISDI/elmds was unable to open the configuration file allocated to DDNAME CDYFCNFG.

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF103E

Configuration file must be FIXED or VARIABLE

Reason:

The record format (DCB RECFM) of the configuration file allocated to DDNAME CDYFCNFG must be F, FB, V, or VB.

Action:

CAISDI/elmds terminates. Verify that the DCB RECFM is one of the allowed formats.

CDYF104E

Configuration file logical record length too big

Reason:

The logical record length (DCB LRECL) of configuration file allocated to DDNAME CDYFCNFG cannot exceed 256. The LRECL cannot exceed 256 for fixed files and cannot exceed 260 (4-byte record descriptor word) for variable files.

Action:

CAISDI/elmds terminates. Verify that the DCB LRECL is within bounds.

CDYF105E

Unrecognized command on line linenum

Reason:

CAISDI/elmds detected an unrecognized command on the configuration statement.

linenum is the line number in the configuration file.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF106E

Missing parameter on line linenum

Reason:

CAISDI/elmds detected a missing parameter on the configuration statement.

linenum is the line number in the configuration file.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF107E

Invalid parameter on line linenum token tokenum

Reason:

CAISDI/elmds detected an invalid parameter on the configuration statement.

linenum is the line number in the configuration file.

tokenum is the 1-relative number of the token (blank delimited string) on the line.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF140E

LOG handler unable to set ESTAEX, R15=rc

Reason:

The CAISDI/elmds LOG handler (to handle CDYFLOG) was unable to establish its main recovery routine.

rc is the R15 contents from the ESTAEX macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF141E

LOG handler OPEN error

Reason:

OPEN did not successfully open the output (CDYFLOG).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF142E

LOG handler OPEN Exit error errcode

Reason:

The CAISDI/elmds LOG handler (to handle CDYFLOG) OPEN Exit indicated an error.

errcode is the error code (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF143E

LOG handler STORAGE RELEASE R15=rc

Reason:

CAISDI/elmds encountered a STORAGE RELEASE error for an output message.

rc is the R15 contents from the STORAGE macro (in hex).

Action:

CAISDI/elmds continues.

CDYF144E

LOG SPIN CLOSE error

Reason:

CLOSE did not successfully close the output (CDYFLOG).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF145I

LOG SPIN UNALLOC error R15=rc ERROR=error

Reason:

DYNALLOC returned and error trying to deallocate the CDYFLOG file.

rc is the R15 contents from the DYNALLOC (in hex).

error is the S99ERROR field from the S99RB (in hex).

Action:

CAISDI/elmds continues. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF146E

LOG SPIN ALLOC error R15=rc ERROR=error

Reason:

DYNALLOC returned and error trying to allocate the CDYFLOG file.

rc is the R15 contents from the DYNALLOC (in hex).

error is the S99ERROR field from the S99RB (in hex).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF147E

LOG SPIN OPEN error

Reason:

OPEN did not successfully open the output (CDYFLOG). The file had been closed, unallocated, allocated and was not being opened (spin activity).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF148I

LOG SPIN complete

Reason:

The output log has successfully been spun.

Action:

CAISDI/elmds continues.

CDYF160I

Command complete

Reason:

The command the operator entered has completed.

Action:

CAISDI/elmds continues.

CDYF161E

Command length exceeds 256 bytes

Reason:

The command the operator entered exceeds 256 bytes.

Action:

The command is ignored. CAISDI/elmds continues.

CDYF162E

Invalid command

Reason:

The string the operator entered could not be parsed to determine the command.

Action:

The command is ignored. CAISDI/elmds continues.

CDYF163E

Error processing command

Reason:

An abend occurred processing the operator command.

Action:

The command is ignored. CAISDI/elmds continues.

CDYF164I

STOP acknowledged

Reason:

The stop command was received.

Action:

CAISDI/elmds continues.

CDYF165E

Command not recognized

Reason:

The command the operator entered was not recognized.

Action:

The command is ignored. CAISDI/elmds continues.

CDYF166E

Invalid parameter

Reason:

The command the operator entered contains an invalid parameter.

Action:

The command is ignored. CAISDI/elmds continues.

CDYF167E

Missing required parameter

Reason:

The command the operator entered is missing a required parameter.

Action:

The command is ignored. CAISDI/elmds continues.

CDYF168E

SPIN and SPINCLASS not allowed

Reason:

The SPIN and SPINCLASS commands are not valid because the SPIN configuration statement was not specified.

Action:

The command is ignored. CAISDI/elmds continues.

CDYF200E

pgm unable to set ESTAEX, R15=rc

Reason:

A CAISDI/elmds program was unable to establish its main recovery routine.

pgm is the program name.

rc is the R15 contents from the ESTAEX macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF201E

Event Manager unable to set Resource Manager, R15=rc

Reason:

The event manager was unable to establish a Resource Manager.

rc is the R15 contents from the RESMGR macro (in hex).

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF202E

Unrecognized API api_id in event block (unique unique jobname)

Reason:

The event handler was passed an event control block with did not indicate support for MED or ELS.

api_id is 1 for MED and 2 for ELS.

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues. Collect relevant messages and contact CA Support.

CDYF203E

Unable to obtain CSA R15=rc (unique unique jobname)

Reason:

The event completion routine was unable to obtain CSA storage for the parameters passed to the wake-up SRB.

rc is the R15 contents from the STORAGE macro (in hex).

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues. You cannot POST the waiting unit of work, so you might have to cancel it.

CDYF204I

Address space asid no longer available (unique unique jobname)

Reason:

The event completion routine while attempting to schedule the wake-up SRB determined that the target address space was no longer available.

asid is the target address space (in hex).

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues.

CDYF205I

Address space asid - IEAMSCHD error cmpc gr15 (unique unique jobname)

Reason:

The event completion routine issued the IEAMSCHD macro which resulted in an abend. The abend code (some are acceptable) indicated a condition that was not acceptable.

asid is the target address space (in hex).

cmpc is the SDWACMPC (in hex).

gr15 is the SDWAGR15 (in hex).

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues.

CDYF206I

Address space asid - IEAMSCHD R15=rc (unique unique jobname)

Reason:

The event completion routine issued the IEAMSCHD macro which returned a non-zero return code.

asid is the target address space (in hex).

rc is the R15 contents from the IEAMSCHD macro (in hex).

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues.

CDYF207E

pgm unable to obtain type latch R15=rc (unique unique jobname)

Reason:

A CAISDI/elmds program attempted to obtain a latch but encountered an error.

pgm is the program.

type is the type of latch, such as shared or exclusive.

rc is the R15 contents from ISGLOBT (in hex).

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues. The unit of work is completed in error (as required the caller is POSTed). If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF208E

api_id API handler abended (unique unique jobname)

Reason:

The CAISDI/elmds event handler detected an unhandled abend in the routine handling the specify request.

api_id is 1 for MED and 2 for ELS.

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues. The unit of work is completed in error (as required the caller is POSTed). If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF209E

EventADD R15=rc (unique unique jobname)

Reason:

A call to CAISDI/elmds occurred but the unit of work could not be added.

rc is the return code from the routine responsible for adding a unit of work to the queue.

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues. The unit of work is completed in error (as required the caller is POSTed). If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF210E

Event Post Dequeue R15=rc (unique unique jobname)

Reason:

The CAISDI/elmds routine responsible for de-queuing a completed unit of work returned an error condition.

rc is the return code from the routine responsible for de-queuing a unit of work and scheduling the wake-up SRB.

unique is a unique number associated with the unit of work.

jobname is the JOBNAME associated with the unit of work.

Action:

CAISDI/elmds continues. The unit of work cannot be POSTed. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF211I

jobname ASID asid R15 api_rc RC rc RSN rsn POST code (unique unique)

Reason:

The event handler detected that after processing by the specific handler, that the POST code or the API return codes were non-zero.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

api_rc is the R15 return code set by the specific handler (in hex).

rc is the return code that is returned to the API (in hex).

rsn is the reason code that is returned to the API (in hex).

code is the code used when POSTing the user (in hex).

unique is a unique number associated with the unit of work.

Action:

CAISDI/elmds continues.

CDYF300E

OPEN failed for ddname dataset

Reason:

CAISDI/elmds was unable to open the data set allocated to DDNAME ddname.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF301E

MEDPARMS must have RECFM FIXED

Reason:

The data set allocated to DDNAME MEDPARMS must have RECFM F or FB.

Action:

CAISDI/elmds terminates. Verify that the DCB RECFM is one of the allowed formats.

CDYF302E

ELSSTART must have RECFM FIXED with LRECL 80

Reason:

The data set allocated to DDNAME ELSSTART must have RECFM F or FB and LRECL 80.

Action:

CAISDI/elmds terminates. Verify that the DCB RECFM is one of the allowed formats and the LRECL is correct.

CDYF303E

parse - logical card too long starting on line linenum

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) exceeds the maximum length (at least 1000 bytes).

linenum is the line number in the file.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF304E

parse - incomplete statement starting on line linenum

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) indicated continued input but no continued statement was read.

linenum is the line number in the file.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF305E

parse - invalid parameters on statement statement

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) starting with statement contains an invalid parameter.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF306E

parse - invalid keyword keyword on statement statement

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) starting with statement contains an invalid keyword.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF307E

parse - duplicate keyword keyword on statement statement

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) starting with statement contains a duplicate keyword.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF308E

parse - missing value for keyword keyword

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) is missing the value for the keyword keyword.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF309E

parse - invalid value for keyword keyword

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) has an invalid value for the keyword keyword.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF310E

parse - error parsing value for keyword keyword

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) provided a value for the keyword keyword. An error was encountered parsing that keyword value.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF311E

parse - missing required parameter on statement statement

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) starting with statement requires a parameter that was not provided.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF312E

parse - quotes not matched on statement statement

Reason:

The configuration statement in either the CAISDI/els or CAISDI/med support (message is in context) starting with statement detected unmatching quoted.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF313E

parse - statement missing or invalid

Reason:

The configuration file for either the CAISDI/els or CAISDI/med support (message is in context) either contains an invalid statement or is missing a required statement.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF314E

parse - unrecognized parameter statement: parameter

Reason:

The configuration file for either the CAISDI/els or CAISDI/med support (message is in context) contains an invalid statement starting with parameter.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF315E

parse - parenthesis not matched starting on line linenum

Reason:

The configuration file for either the CAISDI/els or CAISDI/med support (message is in context) contains a statement on which parentheses are not matched (balanced).

linenum is the line number in the configuration file.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF316E

parse - invalid continuation of quoted string on line linenum

Reason:

The configuration file for either the CAISDI/els or CAISDI/med support (message is in context) contains a statement with a quoted string that is continued on the next line. The matching quote (single or double) could not be located on the continued line.

linenum is the line number in the configuration file.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF317E

error parsing statement starting on line linenum

Reason:

The configuration file for either the CAISDI/els or CAISDI/med support (message is in context) contains a statement for which a parsing error was detected. This general message follows specific messages to identify the line number of the statement.

linenum is the line number in the configuration file.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF318E

error obtaining file input after record recnum

Reason:

An error occurred obtaining input from a configuration file.

file identifies the configuration file.

recnum is the number of records successfully read.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF319I

text

Reason:

The text is a line from the MEDPARMS configuration file.

Action:

No action necessary.

CDYF320I

text

Reason:

The text is a line from the ELSSTART configuration file or a member of the EVENTLIB.

Action:

No action necessary.

CDYF321E

MED - duplicate SERVER (server name must be unique)

Reason:

The MEDPARMS configuration file contains a duplicate SERVER statement. They must be unique.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF322E

MED - no SERVER defined (at least one SERVER must be defined)

Reason:

The MEDPARMS configuration file does not contain any SERVER statement. There must be at least one defined.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF324E

MED - invalid SERVER on PRODUCT statement; PRODUCT=product SERVER=server

Reason:

The MEDPARMS configuration file has a PRODUCT statement which specifies a server which was not defined.

product identifies the PRODUCT.

server is the server from the PRODUCT statement.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF325E

MED - no PRODUCT defined (at least one PRODUCT must be defined)

Reason:

The MEDPARMS configuration file does not contain any PRODUCT statement. There must be at least one defined.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF326W

MED - INIT keywords DEBUGMSG and REUSE are deprecated

Reason:

The MEDPARMS configuration file had an INIT statement with keyword DEBUGMSG or REUSE. These keywords are deprecated.

Action:

Processing continues, these keywords are ignored. Correct the configuration statement.

CDYF327E

ELS - duplicate DEFINE (product name must be unique)

Reason:

The ELSSTART configuration file contains a duplicate DEFINE statement. The product name must be unique.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF328E

ELS - SETUP product name name1 does not match DEFINE product name name2

Reason:

The ELSSTART configuration file contained a DEFINE with product name name2 but the SETUP member in the EVENTLIB defined product name1 which does not match name2.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF329E

ELS - no DEFINE statements (at least one product must be defined)

Reason:

The ELSSTART configuration file does not contain any DEFINE statement. There must be at least one defined.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF330W

ELS - keywords USD_ID and USD_PW are deprecated

Reason:

The ELS DEFAULTS or DEFINE statement had keyword USD_ID or USD_PW. These keywords are deprecated.

Action:

Processing continues, these keywords are ignored. Correct the configuration statement.

CDYF331I

Processing for statement

Reason:

The configuration statement for statement is being processed. For the ELS interface, statement can be DEFAULTS, DEFINE, SETUP, SET, or any valid statement and indicates CAISDI/elmds is processing that statement. This message is to provide the same information that the CAISDI/els product provided.

Action:

No action necessary.

CDYF332I

Parameter in effect: parameter=value

Reason:

This displays the value of parameter parameter on a statement being parsed. This message is to provide the same information that the CAISDI/els product provided.

Action:

No action necessary.

CDYF333E

No room in dynamic area to add string

Reason:

CAISDI/elmds uses a dynamic area to build strings from the configuration file but there is insufficient room.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF334E

Not enough storage for data buffers

Reason:

CAISDI/elmds was unable to obtain storage dynamically for reading a configuration file.

Action:

CAISDI/elmds terminates. Collect relevant messages and contact CA Support.

CDYF400I

MED initialized and available

Reason:

CAISDI/elmds has successfully parsed the med configuration file and initialized the environment. CAISDI/elmds is now available for CA products that use the med interface to communicate with Service Desk.

Action:

No action necessary.

CDYF401I

ELS initialized and available

Reason:

CAISDI/elmds has successfully parsed the els configuration files and initialized the environment. CAISDI/elmds is now available for CA products which use the els interface to communicate with Service Desk.

Action:

No action necessary.

CDYF402E

Event library data set not found LOCATE R15=rc

Reason:

A DEFINE statement in the ELSSTART configuration file specified an EVENTLIB which CAISDI/elmds could not locate. The data set must be cataloged.

data set is the data set name of the Event library.

rc is the R15 contents from the LOCATE macro (in hex).

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF403E

func event library data set failed, DYNALLOC R15=rc ERROR=error INFO=info

Reason:

A DEFINE statement in the ELSSTART configuration file specified an EVENTLIB which CAISDI/elmds could not dynamically allocate or deallocate.

func is either “Allocate” or “Deallocate”

data set is the data set name of the Event library.

rc is the R15 contents from the DYNALLOC (in hex).

error is the S99ERROR field from the S99RB (in hex).

info is the S99INFO field from the S99RB (in hex).

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF404I

Event library data set allocated to DD name ddname

Reason:

CAISDI/elmds has successfully allocated the event library data set to the DD named ddname. The event library is then processed.

Action:

No action necessary.

CDYF405E

Unable to open event library data set

Reason:

CAISDI/elmds was unable to open the event library data set.

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF406E

Event library data set not a partitioned data set

Reason:

The Event library specified in ELSSTART must be a partitioned data set.

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF407E

Event library data set has unsupported RECFM (only F, FB, V, VB)

Reason:

The Event library specified in ELSSTART must be FIXED (F or FB) or VARIABLE (V or VB).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF408E

Event library data set has invalid block or record size

Reason:

The Event library data set has an invalid block or record size as determined by the DCB attributes. Both must be positive. The block size must be less than or equal to 32,767. For RECFM F or FB (fixed), the record size (LRECL) cannot exceed 256. For RECFM V or VB (variable), the LRECL is 4 more than the maximum record length as it contains a 4-byte record descriptor word. Hence the LRECL cannot exceed 260.

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF409E

Error reading directory of data set, DESERV R15=rc Reason=reason

Reason:

CAISDI/elmds encountered an error reading the directory of the Event library data set.

data set is the data set name of the Event library.

rc is the R15 contents from the DESERV macro (in hex).

reason is the R00 contents from the DESERV macro (in hex).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF410E

PRODCNTL member member was not found in data set

Reason:

A DEFINE statement in the ELSSTART configuration file specified the Event library data set and a PRODCNTL member member. However, CAISDI/elmds could not locate that member in that Event library.

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF411E

Error positioning member member, POINT R15=rc R00=reason

Reason:

CAISDI/elmds encountered an error pointing to a member of the Event library that is currently allocated.

member is the member of the Event library that is currently allocated.

rc is the R15 contents from the POINT macro (in hex).

reason is the R00 contents from the POINT macro (in hex).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF412W

Expected event library member member not found

Reason:

The ELSSTART configuration file contained a DEFINE statement. The language was determined from the DEFINE, any DEFAULTS and possibly the SETUP statement. A member was found that matched the MASK value but did not match the expected name when the language suffix was applied.

Action:

Processing continues. Correct the configuration statement.

CDYF413I

English version member2 will be substituted for member1

Reason:

This message follows CDYF412W if the English version (member2) of member1 was located. The English version is formed by supplying EN as the suffix.

Action:

Processing continues. Correct the configuration statement.

CDYF414W

No events for member were found for LANG lang

Reason:

This message follows CDYF412W and possibly CDYF413I. See CDYF412W for a description of member and lang.

Action:

Processing continues. Correct the configuration statement.

CDYF415I

Processing event library member member

Reason:

CAISDI/elmds has successfully allocated the event library and is now processing member member.

Action:

No action necessary.

CDYF416E

Unrecognized control statement: text

Reason:

While processing and event member in the Event library, an unrecognized control statement was detected.

text is the first 80 bytes of the record.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF417I

Processing event library member member control statement statement

Reason:

The control statement statement was detected during processing of the event library member member.

Action:

No action necessary.

CDYF418E

Event library member member statement statement must not have other data

Reason:

The control statement statement was detected during processing of the event library member member. However, there was additional text on that line. The specified statement acts as a “start of section” indicator in that member and no additional text is allowed on that same line.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF419E

Event library member member has duplicate control statement statement

Reason:

The specified control statement had already been processed during processing of the event library member. The specified statement acts as a “start of section” indicator in that member and can only be specified once.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF420E

No event member found in EVENTLIB

Reason:

The currently allocated event library does not contain any events. There has to be at least one event passing MASK filtering and language.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF421E

Event library member member section section too large

Reason:

The specified control statement, indicated by section, acts as a “start of section” indicator in that member during processing of the event library member. The data for that section starts on the next line and proceed to either the next control statement (section) or end of file. The total amount of data is too large. The SUMMARY: section can have a maximum of 240 bytes of data. The DESCRIPTION: section can have a maximum of 4,000 bytes. Trailing blanks on a line are ignored.

Action:

CAISDI/elmds terminates. Correct the configuration statement.

CDYF422I

Unallocating event library data set

Reason:

CAISDI/elmds had successfully allocated the event library data set and has now successfully unallocated that library. Processing of the data set has completed.

Action:

No action necessary.

CDYF423I

Processing event library control member member

Reason:

CAISDI/elmds is processing the PRODCNTL member specified on a DEFINE statement in the ELSSTART configuration file.

Action:

No action necessary.

CDYF424E

Error initializing med interface R15=rc

Reason:

CAISDI/elmds called the routine responsible for initializing med support and an error was returned. This message is Possibly due to an error detected in the configuration file.

rc is the R15 contents from the med initialization code (in hex).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF425E

MED interface already active, ENQ error rc

Reason:

CAISDI/elmds uses the same ENQ RNAME and QNAME as the CAISDI/med product used. When CAISDI/elmds issued the ENQ, the ENQ macro returned an error condition. If the CAISDI/med job CASDIMED is being used, then CAISDI/elmds must be started with NO_MED in its configuration file allocated to DDNAME CDYFCNFG.

rc is the return code set by the ENQ macro (in hex).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF426E

Error initializing els interface R15=rc

Reason:

CAISDI/elmds called the routine responsible for initializing els support which returned an error indication. (Possibly due to an error detected in any of the configuration files.)

rc is the R15 contents from the els initialization code (in hex).

Action:

CAISDI/elmds terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF427E

MAXCOUNT exceeded for product event event

Reason:

A request to create a ticket was made for product (from ELSSTART) for event event, however, the MAXCOUNT would have been exceeded.

Action:

The request is rejected. If there are many such messages, dynamically turn on tracing to determine the address spaces making the request.

CDYF428E

MINTIME exceeded for product event event

Reason:

A request to create a ticket was made for a product (from ELSSTART) for event event, however, the MINTIME would have been exceeded. This message indicates that requests are occurring faster than the MINTIME specification.

Action:

The request is rejected. If there are many such messages, dynamically turn on tracing to determine the address spaces making the request.

CDYF429E

jobname ASID asid TIMEOUT time REQ_TYPE req query (unique unique)

Reason:

The application made a request and specified a timeout value. During processing of the request, the timeout value was exceeded.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

time is the time set by the application.

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for an srel, in which case query is a non-zero value. (Displayed in hex.)

unique is a unique number associated with the unit of work.

Action:

Processing stops when the timeout condition is detected and the application notified. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF430E

jobname ASID asid SDI API RC rc REQ_TYPE req query (unique unique)

Reason:

The CAISDI/soap interface returned an error detected by its application code during application request processing.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

rc is the return code from CAISDI/soap (in hex).

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for an srel in which case query has a non-zero value. (Displayed in hex.)

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF431E

jobname ASID asid SDI CCI RC rc FDBVR code1 FDVBRC code2 REQ_TYPE req query (unique unique)

Reason:

The CAISDI/soap interface returned an error during application request processing, indicating that CAICCI returned an error.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

rc is the CAICCI return code (in hex).

code1 is the FDBVR field set by CAICCI (in hex).

code2 is the FDVBRC field set by CAICCI (in hex).

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for an srel in which case query has a non-zero value. (Displayed in hex.)

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF432E

jobname ASID asid SDI WS RC rc REASON reason REQ_TYPE req query (unique unique)

Reason:

The CAISDI/soap interface returned an error during application request processing, indicating a web service type of error.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

rc is the return code from CAISDI/soap web server interface (in hex).

reason is the reason code from CAISDI/soap web server interface (in hex).

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for an srel in which case query is a non-zero value. (Displayed in hex.)

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF433E

jobname ASID asid SDI API rc1 CCI rc2 WS rc3 REQ_TYPE req query (unique unique)

Reason:

The CAISDI/soap interface returned an error during application request processing, but CAISDI/elmds could not determine the specific cause.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

rc1 is the return code from CAISDI/soap application interface (in hex).

rc2 is the return code from CAISDI/soap CAICCI interface (in hex).

rc3 is the return code from CAISDI/soap web server interface (in hex).

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for a srel in which case query is a non-zero value. (Displayed in hex.)

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF434E

(unique unique) ServiceDesk ErrorCode code

Reason:

The CAISDI/soap interface returned an error from Service Desk and the SOAP Fault during application processing.

unique is a unique number associated with the unit of work.

code is the ServiceDesk “ErrorCode” (returned as a character string) passed in the SOAP Fault.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF435E

(unique unique) ServiceDesk ErrorMessage message

Reason:

The CAISDI/soap interface returned an error from Service Desk during application request processing, and returned the SOAP Fault.

unique is a unique number associated with the unit of work.

message is the ServiceDesk “ErrorMessage” returned as a character string, passed in the SOAP Fault. Only the first 200 characters are displayed.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF436E

jobname ASID asid REQ_TYPE req query object object not returned (unique unique)

Reason:

The expected object was not returned during application request processing.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for an srel in which case query is a non-zero value. (Displayed in hex.)

object identifies the specific object in the CAISDI/soap defined interface to the Service Desk method for this request.

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF437E

jobname ASID asid REQ_TYPE req query object object too long (unique unique)

Reason:

The object returned during application request processing, exceeded the maximum expected length.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for an srel in which case query is a non-zero value. (Displayed in hex.)

object identifies the specific object in the CAISDI/soap defined interface to the Service Desk method for this request.

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF438E

jobname ASID asid REQ_TYPE req query error building whereClause (unique unique)

Reason:

A query (doSelect) is required during application request processing. An error occurred building the “whereClause”.

jobname is the JOBNAME associated with the unit of work.

asid is the ASID associated with the unit of work (in hex).

req is the type of request (1 for CREATE, 2 for UPDATE and 3 for CLOSE). (Displayed in hex.)

query is zero unless Service Desk is queried for a srel in which case query is a non-zero value. (Displayed in hex.)

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF439E

resource value not processed (unique unique)

Reason:

A Service Desk resource was not defined or could not be queried during application request processing such as error building whereClause. For example, if the configuration file specified AFFECTED_END_USER, then resource is (abbreviated) AFFECTED and value is the value from the configuration file.

resource is one of the Service Desk resources indirectly identified by this string.

value is the value of the resource from the configuration file. This value is either the only associated value (contact) for els support or is the last_name for med support.

unique is a unique number associated with the unit of work.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF440E

(unique unique) FIRST first MIDDLE middle

Reason:

This message follows CDYF439E if there is a first_name or middle_name.

Action:

Processing for that request stops and the application notified. Review the CAISDI/soap address space and messages. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF441I

Defined resource value (unique unique)

Reason:

A Service Desk resource that was not defined during application request processing has successfully been defined. For example, if the configuration file specified AFFECTED_END_USER then resource would be (abbreviated) AFFECTED and value would be the value from the configuration file.

resource is one of the Service Desk resources indirectly identified by this string.

value is value of the resource from the configuration file. This value is either the only associated value (contact) for els support or is the last_name for med support.

unique is a unique number associated with the unit of work.

Action:

No action necessary.

CDYF442I

(unique unique) FIRST first MIDDLE middle

Reason:

Will follow CDYF440I if there is a first_name or middle_name.

Action:

No action necessary.

CDYF800E

Unable to establish ESTAEX, R15=rc

Reason:

CDYFELS1 was unable to establish its main recovery routine.

rc is the R15 contents from the ESTAEX macro (in hex).

Action:

CDYFELS1 terminates. Collect relevant messages and contact CA Support.

CDYF801E

Unable to OPEN SYSPRINT

Reason:

OPEN did not successfully open the output file (SYSPRINT).

Action:

CDYFELS1 terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF802E

Error during OPEN SYSPRINT, reason=reason

Reason:

CDYFELS1 encountered an error during the OPEN of SYSPRINT.

reason is the reason (in hex).

Action:

CDYFELS1 terminates. Collect relevant messages and contact CA Support.

CDYF803E

Unable to OPEN SYSIN

Reason:

OPEN did not successfully open the input file (SYSIN).

Action:

CDYFELS1 terminates. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF804E

Error during OPEN SYSIN, reason=reason

Reason:

CDYFELS1 encountered an error during the OPEN of SYSIN.

reason is the reason (in hex).

Action:

CDYFELS1 terminates. Collect relevant messages and contact CA Support.

CDYF805E

ABEND occurred in code

Reason:

An abend occurred. A dump is available in SYSUDUMP.

code is the section of the program where the abend occurred.

Action:

CDYFELS1 terminates. Collect relevant messages and dump and contact CA Support.

CDYF806E

PARM data length exceeds maximum

Reason:

A PARM= was coded on the JCL EXEC statement. The length of the parameter data exceeds the maximum length of 120 characters.

Action:

CDYFELS1 terminates. Change the “PARM=” data in the JCL.

CDYF807E

Invalid continuation of quoted string on line linenum

Reason:

The SYSIN contains a statement which has a quoted string with an indication that it is continued but the quote (single or double) could not be located on the continued line.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF808E

Logical card too long starting on line linenum

Reason:

The SYSIN contains a statement which exceeds 1024 bytes.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF809E

Incomplete statement starting on line linenum

Reason:

The SYSIN contains a statement which indicated continued input but no continued statement was read.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF810E

GETCARD called with EOF already set

Reason:

Internal logic error.

Action:

CDYFELS1 terminates. Collect relevant messages and contact CA Support.

CDYF811E

Error error reading input

Reason:

An error occurred reading SYSIN.

error is the error code (in hex).

Action:

CDYFELS1 terminates. Collect relevant messages and contact CA Support

CDYF812E

Missing parameter on line linenum

Reason:

The SYSIN contains a statement which was not blank but could not locate the first token “TRIGGER”.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement

CDYF813E

Unrecognized parameter parm on line linenum

Reason:

A noncomment, nonblank statement was found but the first token was not “TRIGGER”.

parm is the detected parameter.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF814E

Invalid VAR starting on line linenum - must be up to 8 bytes of the form VAR=value

Reason:

Error parsing statement locating the variable name (followed by “=” and the value).

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF815E

Duplicate VAR var starting on line linenum

Reason:

A duplicate variable name was detected.

var is the variable name.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF816E

Missing value for VAR var starting on line linenum

Reason:

The value for a variable was not specified.

var is the variable name.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF817E

Overflow starting on line linenum

Reason:

Each variable requires 12 bytes. The number of variables and the length of their values exceeded the allotted buffer (approximately 3,900 bytes).

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF818E

Value for PRODUCT= starting on line linenum - cannot exceed 8

Reason:

The product must be a one to eight-character string.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF819E

Value for EVENT= starting on line linenum - must be 6 characters

Reason:

The event must be exactly six characters.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF820E

Missing EVENT= for statement starting on line linenum

Reason:

The event specification is required.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF821E

Missing PRODUCT= for statement starting on line linenum

Reason:

The product specification is required.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF822E

Error parsing value for keyword keyword for statement starting on line linenum

Reason:

A statement was being parsed and the specified keyword encountered, however, there was an error attempting to determine its value.

keyword is the keyword being processed.

linenum is the line number of the statement.

Action:

CDYFELS1 terminates. Correct the statement.

CDYF823E

LINK error (statement starting on line linenum) ReasonCode: reason AbendCode: abcode

Reason:

CDYFELS1 issues a LINK macro for CSDEOPRQ after processing the statement. The resulting LINK indicated an error.

linenum is the line number of the statement.

reason is the reason code (in hex).

abcode is the abend code (in hex).

Action:

CDYFELS1 terminates. This message helps to verify that CSDEOPRQ is available either in the STEPLIB or LINKLIST. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF824I

Processing statement starting on line linenum - Product: product Event: event

Reason:

The statement has been successfully parsed and is ready to be processed.

linenum is the line number of the statement.

product is the product from PRODUCT=product.

event is the event from EVENT=event.

Action:

No action necessary.

CDYF825I

Request created for product product - Number: number

Reason:

A Service Desk request was opened for the specified product. This message follows message CDYF824I which identifies the statement that was processed. Message CDYF826I follows with additional information.

product is the product from PRODUCT=product.

number is the Service Desk newRequestNumber (the “number” returned by CAISDI/els.)

Action:

No action necessary.

CDYF826I

Handle: handle

Reason:

This message follows message CDYF825I and provides additional information.

handle is the Service Desk newRequestHandle. (This “handle” is necessary for other Service Desk methods.)

Action:

No action necessary.

CDYF827E

Request failed for product product - Return code: rc Reason: reason Info: info

Reason:

A Service Desk request failed for the specified product. This message follows message CDYF824I which identifies the statement that was processed. Message CDYF828E follows with additional information. Other messages can follow message CDYF828E with specific information, otherwise message CDYF836I follows message CDYF828E.

product is the product from PRODUCT=product.

rc is the return code (R15) set by CSDEOPRQ (in hex).

reason is the reason code (R00) set by CSDEOPRQ (in hex).

info is the information code (R01) set by CSDEOPRQ (in hex).

Action:

Processing continues with the next statement. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF828E

EPLRET: rc EPLRSN: reason

Reason:

This message follows message CDYF827E and provides additional information.

rc is the EPLRET field of the EPL control block passed to CSDEOPRQ (in hex).

reason is the EPLRSN field of the EPL control block passed to CSDEOPRQ (in hex).

Action:

Processing continues with the next statement. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF829I

Request failed because of MINTIME

Reason:

The request failed due to the MINTIME setting. When this request was received, the MINTIME had not expired for a request that CAISDI/elmds previously processed.

Action:

Processing continues with the next statement. The MINTIME setting is in the configuration files of CAISDI/elmds. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF830I

Request failed because of MAXCOUNT

Reason:

The request failed due to the MAXCOUNT setting. When this request was received, CAISDI/elmds already processed the maximum number of requests allowed for this event.

Action:

Processing continues with the next statement. The MAXCOUNT setting is in the configuration files of CAISDI/elmds. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF831I

Request failed because the CAISDI/elmds interface for ELS is not available

Reason:

The ELS support in CAISDI/elmds is not available. This message can occur if CAISDI/elmds is not active or the CAISDI/elmds configuration statement NO_ELS was specified.

Action:

Processing continues with the next statement. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF832I

Request failed because the PRODUCT is disabled

Reason:

The product has been disabled in CAISDI/elmds. (See the operator commands for CAISDI/elmds to enable/disable an ELS product.)

Action:

Processing continues with the next statement. Verify that the product is supposed to be disabled, otherwise re-enable the product. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF833I

Request failed because the PRODUCT is not defined

Reason:

The request failed because the product is not defined to CAISDI/elmds.

Action:

Processing continues with the next statement. Verify the configuration files for CAISDI/elmds. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF834I

Request failed because the EVENT is not defined for the specified product

Reason:

The request failed because the event related to the product is not defined to CAISDI/elmds.

Action:

Processing continues with the next statement. Verify the configuration files for CAISDI/elmds. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF835I

Error from CAISDI/soap interface - SDICNTL_RC=rc API/CCI/WS_RC=rc2

Reason:

The request failed and CAISDI/elmds reflected back to CSDEOPRQ that an error occurred in the CAISDI/soap interface.

rc is the SDICNTL_RC from the control block used by CAISDI/elmds for the CAISDI/soap interface (in hex).

rc2 is the SDICNTL_API_RC, SDICNTL_CCI_RC or the SDICNTL_WS_RC from the control block used by CAISDI/elmds for the CAISDI/soap interface (in hex).

Action:

Processing continues with the next statement. Review the CAISDI/elmds and CAISDI/soap logs; if the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF836I

No additional information

Reason:

This message follows messages CDYF827E and CDYF828E when no additional specific information is provided. The codes returned in those messages are for CA Support.

Action:

Processing continues with the next statement. If the problem cannot be resolved, collect relevant messages and contact CA Support.

CDYF900I

text

Reason:

This message is a general informational message and the text can vary.

Action:

No action necessary.

CDYF990E

messageid – not found

Reason:

A CAISDI/elmds routine requested message messageid be issued but the message is not defined.

Action:

Processing continues. The requested message cannot be displayed. Collect relevant messages and contact CA Support.

CDYF991E

messageid – format error

Reason:

A CAISDI/elmds routine requested message messageid be issued but an error was encountered formatting the text.

Action:

Processing continues. The requested message cannot be displayed. Collect relevant messages and contact CA Support.