z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


1C3

z/OS MVS System Codes
SA38-0665-00

1C3

Explanation

An error occurred during IBM® License Manager (ILM) processing. The accompanying reason codes identify either an internal IBM License Manager error or an external error code as follows:
Value Description
0403 Bad input parameters.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0414 Bad return code from ETCRE macro.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0415 Bad return code from ETCON macro.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0418 Bad return code from ESTAE macro.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0419 Bad return code from VSM Locate macro.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0420 Bad return code from LOAD or NUCLKUP macros.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0422 Bad return code from DSPSERV Create.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0423 Bad return code from ALESERV Add.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0424 Bad return code from EnfReq Listen.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0425 C Daemon not responding to termination request.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0427 Attach of BPXBATSL to execute Agent C Daemon failed.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0428 Taking dump as requested by Agent C Daemon.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

0429 Taking dump as requested by Server C Daemon.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05C4 Cell storage address required.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05C5 Cannot do DSPSERV RELEASE for this cell pool.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05C6 Bad return code from Csrpbld service.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05C7 Bad return code from Csrpexp service.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05C8 A Storage Manager Control Block stack is invalid.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05C9 A Storage Manager Control Block stack overflowed.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05CA A Master Cell Pool is out of extent storage cells.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05CC Cell pool token is invalid.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05CD Cell pool is out of cells.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05CE Cell address is invalid.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05CF Bad return code from Csrpfre service.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D0 Bad return code from Csrpget service.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D1 Bad return code from Csrpqpl service.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D2 Incorrect data in a certificate.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D3 The set of certificates had no IBM global certificate.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D4 The agent provided a DOM ID of 0 to be saved.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D5 The server provided a DOM ID of 0 to be saved.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D6 The agent provided a stall time of 0.

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

05D7 The agent or server provided a DOM ID of 0 to be deleted..

Action: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and, if this problem caused multiple abends, the portion of the logrec log containing the relevant logrec records.

8005 The callable service was issued by a program running with an EUT FRR set.

Action: You must not issue the callable service when an FRR is set. FRRs must be deleted before calling the service.

8006 The callable service was issued by a program running with a system lock held.

Action: You must not issue the callable service when a lock is held. Release the locks before calling the service.

C001 The IBM License Manager is not supported on this system.

Action: Start the IBM License Manager on a processor that supports this capability.

C003 The callable service was not issued by a program running under a task.

Action: You must issue the callable service only in task mode. SRB mode is not supported.

C004 The CVTILM bit is off, which means no calls to the IBM License Manager should be made.

Action: User error. If the official stubs are used to call the IBM License Manager, the stub will test the CVTILM bit. If you are calling the IBM License Manager without the stub, you must check CVTILM and call only if the flag is ON.

C007 The callable service was issued in cross-memory mode.

Action: You cannot issue the callable service in cross-memory mode. Correct the problem and resubmit the job.

C009 The parameter list contains an incorrect number of parameters.

Action: An error was encountered that prevents the running of the callable service. However, the system cannot set an error return code for the caller because the input parameter list is incorrectly specified.

An ABDUMP or symptom dump has been requested for the caller. In the dump, register 2 contains the return code value and register 3 contains the reason code value of the original failure. Do both of the following:
  • Analyze the return code and reason code for the cause of the original problem.
  • Check for incorrect input parameters passed to the callable service.
C00E An incorrect address was encountered when trying to move user parameter data. This can be caused by one of the following conditions:
  • The total number of parameters is incorrect for the callable service being issued.
  • Action:There is an error in one of the passed user parameters causing the IBM License Manager to program check when the parameter is accessed. Check for the following conditions:
    • A parameter that points to non-existent storage.
    • A parameter that cannot be accessed in the current user PSW key.

Any other reason codes indicate that an internal error has occurred.

System action

For the reason codes listed above, use the system actions specifically listed.

System programmer response

Try the request again. If the problem persists, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the dump and logrec entries associated with this abend.

For the reason codes listed above, use the system programmer response specifically listed.

Source

IBM License Manager

Module

Many

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014