VSE CAID Messages

CAID001E

LOAD OF IDMSVCTB FAILED

Reason:

Initialization was unable to load the IDMSVCTB SVC table.

Module:

IDMSPSTA

Severity:

CAID002E

INITIALIZATION OF CA IDMS SVC <SVC-Number> FAILED RC=<return-Code>

Reason:

A problem occurred during the initialization of an IDMS SVC. The SVC number and a return code are displayed:

RC=4—Unable to load Program
RC=8—Program unavailable
RC=12—Unable to locate program
RC=NN—Error returned by IDMSISVC program

Module:

IDMSPSTA

Severity:

CAID003I

CA IDMS SVC <SVC-Number> IS ACTIVE

Reason:

SVC Initialization completed and the SVC is ready to be called.

Module:

IDMSPSTA

Severity:

CAID004E

ILLEGAL CA IDMS SVC <SVC-number> CALL.

JOB IS CANCELED RC=<return-code> ERRCD=<Error-Code>

Reason:

An error was detected during the processing of an SVC request.

SVC-number

Identifies the SVC number issued.

return-code

Displays the decimal R15 value, if applicable.

error-code

Displays an internal code. Some codes follow:

04—Invalid DSVCTBL found
08—Invalid function requested
12—No ESE passed - Func 1
16—CV Table index invalid
20—CSV CV number does not match CV table
24—CV Table full, see #DEFSVC MAXCV
28—Partition table full, see #DEFSVC MAXPART
32—Enable Intercept failed
36—Disable Intercept failed
40—GETVIS failed
44—IDMSVCTB not found
48—IDMSVCTB not available
52—IDMSSVXA not found
56—DSVCTBL not found
60—PRODEXIT DEFINE failed
72—IDMSDSVC detected error

Module:

IDMSVCFN

Severity:

CAID005I

<variable text>

Reason:

Each line contains variable information. Some examples follow:

When CASAUTIL initialization is done, the following message indicates where SVC common storage was allocated. The SVC and release number are also displayed:
CAID005I SVC.COMM ALLOCATED AT 00252BE8 SVC=235 REL=17.0
When the IDMS S console command is issued the same line plus other information is also displayed:
IDMS S

CAID005I IDMSPXIT ALLOCATED AT 1FE28800

CAID005I IDMSSVXA ALLOCATED AT 0022FD08

CAID005I IDMSVCTB ALLOCATED AT 1FF37038

CAID005I SVC.COMM ALLOCATED AT 00252BE8 SVC=235 REL=17.0

CAID005I IDMSVCFN ALLOCATED AT 1FEF23B8

CAID005I IDMSDSVC ALLOCATED AT 002D9008 CVNUM=001 PIK=08

Module:

IDMSISVC, IDMSVCFN

Severity:

CAID006E

CA IDMS SVC=<SVC-Number> FUNCTION=<SVC-Function>

ADDRESS <Hex-Address> VALIDATION FAILURE

Reason:

An invalid address was passed to the SVC Storage protect function. This is probably an internal error.

Module:

IDMSDSVC

Severity:

CAID007I

<program-name> LOADED AT <hex-address>

Reason:

An informational message that indicates where the named SVC initialization program was loaded.

Module:

IDMSISVC

Severity:

CAID009I

CA IDMS SVC <SVC-number> IS NOT DEFINED IN IDMSVCTB

Reason:

An SVC request for the specified SVC number was issued, but the SVC is not defined in the SVC table.

The SVC defined in an IDMS CV SYSGEN must also be defined in IDMSVCTB which is generated from the #DEFSVC macro.

Use the IDMS S console command to see currently defined SVCs.

Module:

IDMSVCFN

Severity:

CAID010I

<variable-info>

Reason:

This is a generic message which contains different information depending on which program issues the message:

CAID010I CA IDMS UNABLE TO PROCESS IDMSVCTB TABLE
This message is isssued by IDMSPSTA when too many errors were encountered while trying to initialize the SVCs defined in the IDMSVCTB table. See previous messages. Processing of the SVC table stops.
CAID010I CA IDMS VCFN <variable-info>
R15=<hex-value> R0=<hex-value>

This is a generic message issued by IDMSVCFN for one of several reasons listed below. The R15 and R0 values at the time of the error are displayed in hex.
- PXIT GETVIS FAILED
  A GETVIS request for SVC exit processing failed.
- PRODEXIT DEFINE FAILED
  The PRODEXIT DEFINE call failed.
- IDM1223 GETVIS FAILED
  A GETVIS call at label IDM1223 in IDMSVCFN failed.
- IDMSVCFN-25 GETFLD FAILED
  A GETVIS call for function 25 in IDMSVCFN failed.
- IDMSVCFN AUTHORIZE FAILED
  The PRODID AUTH=YES request failed.
- IDMSVCFN UNAUTHORIZE FAILED
  The PRODID AUTH=NO request failed.
- CA IDMS UNABLE TO PROCESS IDMSVCTB TABLE
  The PRODID AUTH=NO request failed.

Module:

IDMSVCFN IDMSPSTA

Severity:

CAID011I

CA IDMS SVC SCREENING ENABLED

Reason:

An informational message indicating SVC screening has been enabled.

Module:

IDMSVCFN

Severity:

CAID012I

CA IDMS SVC SCREENING DISABLED

Reason:

An informational message indicating SVC screening has been disabled.

Module:

IDMSVCFN

Severity:

CAID061I

CA IDMS SVC Exit: <exit-name> loaded at address: <hex-address>.

Reason:

An informational message issued when an IDMS SVC exit is defined and loaded, indicating the name and where it was loaded.

Module:

IDMSDSVC

Severity:

CAID062E

CA IDMS SVC Exit: <Exit-Name> - <Reason>, RTC=<Decimal-Code>.

Reason:

An IDMS SVC exit was defined, but an error occurred when loading it. The name of the phase, a reason message, and a CA-Adapter LOCATE function return code is displayed.

SVC processing continues without the exit.

Reasons for this error can be:

The module was not found.
No storage was available.
An unexpected return code.

Module:

IDMSDSVC

Severity:

CAID100E

CA IDMS DSVM ERROR <error-code> RC=<return-code>

Reason:

An error of some kind was detected in the program IDMSDSVM.

An error code unique to the program is displayed with a possible return code.

Usually these are program internal errors.

Error Codes:

02—Unsupported Function
03—Invalid Plist
04—Unable to locate VCA
10—TASKSERV ATTACH failed

Module:

IDMSDSVM

Severity:

CAID101E

CA IDMS GETVIS/GETAREA ERROR <error-code> RC=<return-code> SIZE=<size-of-request>

Reason:

A request for storage failed using the GETVIS macro or the CA-Adapter GETAREA function. An error code unique within the program making the request is displayed along with the GETVIS or GETAREA return code and size of storage requested.

Error Codes:

01—LWA GETAREA failed
14—GETVIS #1 failed LOC=ANY,SVA,PFIX,PAGE
16—GETVIS #2 failed LOC=ANY,SVA,PFIX,PAGE
22—GETVIS #3 failed LOC=ANY,SVA,PFIX,PAGE
25—GETVIS #4 failed LOC=ANY,SVA,PFIX,PAGE
100—SRB LWA GETAREA failed

Module:

IDMSDSVM

Severity:

CAID102E

CA IDMS VMCF EIH SUBTASK ALREADY RUNNING

Reason:

An IDMSSRB subtask was attached and could not obtain the "IDMSSRB" lock, indicating that another IDMSSRB task was already running. The task issuing the message ends.

Module:

IDMSDSVM

Severity:

CAID103E

CA IDMS VMCF SUBTASK STARTED

Reason:

An informational message indicating that the IDMSSRB subtask has started and is waiting for work.

Module:

IDMSDSVM

Severity:

CAID104E

CA IDMS VMCF SUBTASK BEING SHUTDOWN

Reason:

An informational message indicating that the IDMSSRB subtask has received a request to shut down and is about to detach itself.

Module:

IDMSDSVM

Severity:

CAID105E

CA IDMS CMS OPTION INITIALIZE COMPLETED

Reason:

An informational message indicating that the initialization for the CMS option is finished.

Module:

IDMSDSVM

Severity:

CAID120I

CA IDMS SRB NOT ACTIVE

Reason:

An informational message indicating that a request was made to post or detach the IDMSSRB subtask and it was not attached.

Module:

IDMSDSVM

Severity:

CAID121I

CA IDMS SRB ALREADY ATTACHED

Reason:

An informational message indicating that a request was made to attach the IDMSSRB subtask and that it is already attached.

Module:

IDMSDSVM

Severity:

CAID122I

CA IDMS SRB POSTED

Reason:

An informational message indicating that a request was made to post the IDMSSRB subtask and that it was successful.

Module:

IDMSDSVM

Severity:

CAID123I

CA IDMS SRB Attached

Reason:

An informational message indicating that a request was made to attach the IDMSSRB subtask and that it was successful.

Module:

IDMSDSVM

Severity:

CAID124I

CA IDMS SRB DETACHED

Reason:

An informational message indicating that a request was made to detach the IDMSSRB subtask and that it was successful.

Module:

IDMSDSVM

Severity: