ABN001

The CA VM:Secure ABEND command was issued or a CA VM:Secure macro found an error that required the CA VM:Secure product to abend. Examine the CA VM:Secure console for an error message just prior to the abend that would indicate this.

ABN099

Contact Technical Support.

ACA100

The buffer used for DIAGNOSE ‘A0’ processing is being read by FREAD, but its size does not match the size acquired.

ACA101

While processing a DIAGNOSE ‘A0’ subfunction, the buffer being used was greater than 64K.

ACI101

The first character of the link mode from CP for LINK authorizations is not R, W, or M.

ACJ104

An attempt to add a rule to reject a LOGON, DIAL, or LINK to a user’s user rules failed due to excessive invalid attempts.

ACL003

When processing a VMTAPE MOUNT rule that is supposed to have a data set number (DSN), CA VM:Secure could not find the DSN on the actual rule record.

ACL101

The rule lookup routine was called with a request code that it could not recognize. Usually this condition should have been detected by a routine that called the lookup routine.

ACP001

While building the POSTRULE user exit parameter list, an unrecognized ACI function code was found.

ACR002

While trying to fill in an overriding rule message, an error occurred either opening or reading a rule file.

ACR101

When processing a LOCATE on an edited USRRULES file, CA VM:Secure could not find the associated USRSECT.

ACR102

A rule lookup failed when processing the RULE REVIEW primitive in a macro. This primitive is called by the RULES command to display 0174W and 0175I to tell the user about any rules that override the rules the user just added.

ACU001

An error occurred while opening a rules file during initialization or at rule update time.

ACU002

CA VM:Secure cannot find the USRSECT for the edited USRRULES file.

ACU003

A serious error occurred in RULES INIT or CHKRULES. CA VM:Secure has lost its linked lists of RCBSECTs.

ACV001

A serious error occurred in RULES INIT or CHKRULES. CA VM:Secure has lost its linked lists of RCBSECTs.

ADM001

Contact Technical Support.

AIC001-AIC005
AIC007-AIC010

Contact Technical Support.

AID001-AID002

Contact Technical Support.

AIE001-AIE015

Contact Technical Support.

AIF001-AIF014

Contact Technical Support.

ASN001-ASN002

Contact Technical Support.

AUD101

An unexpected return code was received from the FSSTATE macro while checking for the existence of the AUDIT file.

AUD102

An active disk table (ADT) lookup call to CMS failed to find the ADT for the AUDT disk.

AUT001-AUT002

Contact Technical Support.

BED001

CA VM:Secure opened a directory entry that was empty.

BED003

The EDIT primitive tried to edit a directory entry and could not make it to the top of the directory entry.

BED005

An error occurred while trying to add a Last Logon special comment (*LL=) or a Last (X)Autolog special comment (*LA) to a directory entry.

BED006

An error occurred while trying to add a History special comment (*HS=) to a directory entry.

BED007

The EDIT primitive experienced an error while trying to close a directory entry.

BIG001-BIG002

Contact Technical Support.

BIO002-BIO012

Contact Technical Support.

BKP101

An overflow occurred in the Inter–User Communication Vehicle (IUCV) buffer while transmitting the extract or directory backup back to the requesting user.

BKP102

While scanning directory statements for an extract, a required field on a record was not found.

BKP103

While building the extract or directory backup, CA VM:Secure found more USRSECTs than there were directory entries on the DRCT minidisk.

BKP104

An extract or backup was issued with no USRSECTs in the system (that is, before initialization).

BLK001
BLK004 BLK010-BLK012 BLK022

Contact Technical Support.

BNM001

Contact Technical Support.

BUF001

Contact Technical Support.

BUF101

An invalid buffer was received.

CBB001

Contact Technical Support.

CBK001-CBK005

Contact Technical Support.

CBP001

Contact Technical Support.

CCR001-CCR002

Contact Technical Support.

CDF001

Contact Technical Support.

CDG001-CDG009

Contact Technical Support.

CEL001-CEL002
CEL004

Contact Technical Support.

CER001-CER002

Contact Technical Support.

CFG001

Contact Technical Support.

CFH001

The nucleus reconfiguration block was not found when it is required.

CFH002

While processing EXTSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CFH003

While processing SUBSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CFH004

While processing SPESECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CFH005

While processing IGNSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CFH006

While processing NOLSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CFH007

While processing VOLSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CHP001

An error occurred while encrypting a password.

CMD001

Contact Technical Support.

CMD002

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CMD003-CMD004
CMD100

Contact Technical Support.

CMD005

While processing VOLSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CMD008

Contact Technical Support.

CMN001

During initialization, CA VM:Secure could not find a SYSOPER list. Check the PRODUCT CONFIG file for a SYSOPER record and see if it is valid. Correct the record if it is invalid and start CA VM:Secure again. If the problem persists, contact Technical Support.

CMN003

While processing DSKSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CMN004

While processing VOLSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CMN005

While processing DVCSECTs, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

CMN006

Processing dictates that at least one or a specific DVCSECT must exist and that control was found. A storage overlay or internal logic problem has occurred.

CMS001-CMS002

Contact Technical Support.

CMW001-CMW003

Contact Technical Support.

CPI006

Contact Technical Support.

CPI101

Entry to this module occurred from a process that was not an ACI request.

CPI102

An entry point requiring an IUCV page buffer was called by a process without one.

CPI103

An error occurred issuing an IUCV REPLY to an ACI IUCV SEND.

CPI104

An error other than MSGLIMIT EXCEEDED occurred when issuing an IUCV SEND to the ACI system service.

CPI107

An invalid exit order code was detected when attempting to send a return code back to CP.

CPR001-CPR005
CPR007-CPR010

Contact Technical Support.

CPW001

An error occurred while encrypting a password.

CPW002

An error occurred while processing a password.

CRY001-CRY005

Contact Technical Support.

CSL002

This abend can occur for a number of reasons. To determine the cause, refer to the reason code provided in message 1294S, which CA VM:Secure issues before this abend occurs. Reason code 97250 indicates that the CA VM:Secure service virtual machine cannot allow any more IUCV connections. To correct this problem, increase the MAXCONN setting on the OPTIONS record in the service virtual machine’s directory entry. recommends that this setting be at least 3000. For information on other reason codes, refer to the IBM CMS application development reference documentation.

CSL003-CSL004

Contact Technical Support.

CSL100

A call to DMSCSL resulted in a return code other than 0 or 4, which are the only ones accepted.

CVD001
CVD100

Contact Technical Support.

CVT001

Contact Technical Support.

DBG001

Contact Technical Support.

DBI001

Contact Technical Support.

DBI002

CA VM:Secure database initialization failed. Make sure that the CA VM:Secure database, a file with a filetype of PFMDB, resides on the correct CA VM:Secure minidisk (usually the 1B0 minidisk), then restart CA VM:Secure.

DBI003

The shutdown of the CA VM:Secure database failed.

DBI004-DBI006

Contact Technical Support.

DBK001-DBK003

Contact Technical Support.

DCF001-DCF003

Contact Technical Support.

DDF001

Contact Technical Support.

DDF002

An error occurred when CA VM:Secure used the CP SPOOL command to spool a device to a user. An accompanying CP message is logged on the CA VM:Secure service virtual machine indicating why the CP SPOOL command failed. If the CP message does not provide sufficient information to correct the problem, contact Technical Support.

DDF003

Contact Technical Support.

DDL001

Contact Technical Support.

DDL002

An error occurred when CA VM:Secure used the CP SPOOL command to spool a device to a user. An accompanying CP message is logged on the CA VM:Secure service virtual machine indicating why the CP SPOOL command failed. If the CP message does not provide sufficient information to correct the problem, contact Technical Support.

DDL003-DDL004

Contact Technical Support.

DEV001

While looking for a specific DVCSECT, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

DEV002

A DVCSECT was not found when expected.

DEV003

The values within a DVCSECT are invalid.

DEV004

A second call to the routine to initialize the device type table was detected. A logic error probably has occurred.

DIO001-DIO003

Contact Technical Support.

DIO006

CA VM:Secure tried to perform an I/O operation on a minidisk but the minidisk was not available. (A Start I/O Fast operation returned a condition code 3.) Verify that all DASD and related devices are enabled and available to your VM system and operating correctly. Restart CA VM:Secure. If the abend recurs, contact Technical Support.

DIO007

CA VM:Secure tried to perform an I/O operation on a minidisk, but a Start I/O Fast operation returned a condition code 1. This indicates that the BUSY bit, the STATUS MODIFIER bit, or both were set on but no other status bits were set on. CA VM:Secure might have tried to perform I/O on a minidisk that was shared with another virtual machine while the other machine had the device reserved. Verify that all DASD and related devices are enabled and available to your VM system and operating correctly. If the abend recurs, contact Technical Support.

DIP001-DIP005

Contact Technical Support.

DIR002

An error was encountered in writing a directory page.

DIR004

An error occurred in attempting to read a directory page.

DIR007

An attempt was made to remove the CA VM:Secure user ID from the directory.

DIR101

An error was encountered in attempting to update the directory.

DIR102

A logic error occurred in allocating space on a page.

DIR103

CA VM:Secure was unable to find a USRSECT for the edited file name while processing a DIRECT MDISK function.

DIR104

An error occurred in initializing page allocation. You either ran a CP FORMAT/ALLOCATE or in some way changed cylinder 0, the allocation map, on your SYSRES pack. Run the CMS DIRECT command to fix the pointers, then start CA VM:Secure again with the SOURCE option. If the problem persists, contact Technical Support.

DIR105

A USERTEST was attempted on an empty file.

DIR106

A direct subfunction requiring an initialized directory was attempted before the directory was initialized.

DIR109

CA VM:Secure received an error closing a directory profile after the profile was written to the object directory.

DIR110

VMXDIR received an unexpected return code from VMXDIS, the routine that handles IUCV, IPL, SCREEN, and OPTION control statements.

DIR111

VMXDIR received an unknown error code from the FST lookup routine while checking the date on the directory profiles on the DRCT minidisk to determine whether CA VM:Secure can do a quick start.

DIR112

While building the control blocks for directory profiles to ascertain which users are using which profiles, CA VM:Secure found a USRSECT that was not in the USRSECT chain.

DIR113

While attempting to place a user ID on hold, CA VM:Secure found that you did not have a control block (PRFSECT) for the directory profile the user ID was using.

DIR114

CA VM:Secure tried to delete a user ID who had a profile in its directory entry. When CA VM:Secure tried to take the user ID out of the profile’s reference chain, it could not find the user ID.

DIR115

Contact Technical Support.

DIR116

While processing a POLSECT, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

DIR117

A USRSECT that should be for a pool member does not have the correct user ID prefix or the pool member flag is not set.

DIS001

An error occurred while writing out a page to the object directory after updating a UIUCBLOK or a UIPLBLOK.

DIS003

While processing DSKSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

DIS101

The VMXDIS routine found a directory control statement that it did not recognize. This routine should only be called for processing a limited number of control statements.

DIS102

An error occurred in calculating the new available page length while attempting to allocate a page to write out a UDEVBLOK.

DIS103

When processing a LINK statement in a directory profile, CA VM:Secure could not find the directory profile control block (PRFSECT) for that profile.

DIS106

Contact Technical Support.

DIU001

CA VM:Secure tried to write a page to the object directory and the write failed.

DIU002

While processing DSKSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

DIU003

While processing VOLSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

DIU101

CA VM:Secure tried to process a device card in a directory entry and found an invalid device card.

DIU102

CA VM:Secure attempted to allocate a UDEVBLOK and ran out of room.

DIU103

CA VM:Secure tried to manipulate a link record in a profile reference in a user ID’s directory. However, the profile does not exist.

DMSxxx

Abend messages with a DMS xxx code are CMS abends. Refer to the appropriate IBM documentation for information about these abend codes.

DNX100

Requested too many pages at once.

DNX101

A logic error occurred while allocating space on a page.

DNX102

Attempted to allocate more than one page.

DNX103

An error was encountered in writing a directory page.

DNX104

An error occurred while attempting to read a directory page.

DNX105

A logic error occurred while adding a user to the directory.

DNX106

An error occurred while allocating profile index.

DNX107

An error while allocating held index.

DNX114

CA VM:Secure could not find the user in the object directory.

DNX115

User found in directory that should not have been there.

DNX116

CA VM:Secure could not find the user on hold in the object directory.

DNX117

CA VM:Secure could not find the profile in the object directory.

DNX118

A POSIX user ID that should exist was not found in the CP object directory.

DNX119

A POSIX user ID that should not exist was found in the CP object directory.

DNY100

Requested too many pages at once.

DNY101

A logic error occurred while allocating space on a page.

DNY102

Attempted to allocate more than one page.

DNY103

An error was encountered in writing a directory page.

DNY104

An error occurred while attempting to read a directory page.

DNY105

A logic error occurred while adding a user to the directory.

DNY106

An error occurred while allocating profile index.

DNY107

An error while allocating held index.

DNY114

CA VM:Secure could not find the user in the object directory.

DNY115

User found in directory that should not have been there.

DNY116

CA VM:Secure could not find the user on hold in the object directory.

DNY117

CA VM:Secure could not find the profile in the object directory.

DSK001-DSK002
DSK004
DSK008

Contact Technical Support.

DSP001

A second call was made to the dispatcher initialization routine.

DSP003

An unexpected return was made to the dispatcher after attempting to cause a CMS abend following an HX command.

DSR001

While processing an SVNSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

DST001-DST013
DST015

Contact Technical Support.

DTH001

Contact Technical Support.

DXM001

Internal support for issuing a CA VM:Secure message was not included in the DXM module.

DXM100

A message number was not found within the DXM module.

DXR002

An error was encountered in writing a directory page.

DXR007

An attempt was made to remove the CA VM:Secure user ID from the directory.

DXR100

A logic error occurred while processing continuation records.

DXR101

An error was encountered attempting to update the directory.

DXR102

A logic error occurred while allocating space on a page.

DXR104

An error occurred while deleting a PFXSECT.

DXR105

A USERTEST was attempted on an empty file.

DXR106

A direct subfunction requiring an initialized directory was attempted before the directory was initialized.

DXR109

CA VM:Secure received an error closing a directory profile after the profile was written to the object directory.

DXR110

CA VM:Secure received an unexpected return code from VMXDXS, the routine that handles IUCV, IPL, SCREEN, and OPTION control statements.

DXR113

While attempting to place a user ID on hold, CA VM:Secure found that it did not have a control block (PFXSECT) for the directory profile the user ID was using.

DXR114

CA VM:Secure could not find the user in the object directory.

DXR300

CA VM:Secure found an error while updating the CP object directory.

DXS001

An error occurred while writing out a page to the object directory.

DXS101

The VMXDXS routine found a directory control statement that it did not recognize.

DXS102

An error occurred while calculating the new available page length while attempting to allocate a page.

DXS106

A direct subfunction requiring an initialized directory was attempted before the directory was initialized.

DXS107

Required entry in the internal options table was not found.

DXT003

While processing DSKSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

DXT100

An error occurred while attempting to read a directory page.

DXT101

DGDBK too large to read or write to.

DXT103

The USRSECT for the user ID currently being processed could not be found.

DXT111

A call to the FST lookup routine resulted in a return code other than 1, file not found.

DXU001

CA VM:Secure tried to write a page to the object directory and the write failed.

DXU002

A logic error has caused the processing of the ending cylinder value without having processed the starting cylinder value.

DXU003

While processing DSKSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

DXU004

While processing VOLSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

DXU101

CA VM:Secure tried to process a device card in a directory entry and found an invalid device card.

DXU102

An error occurred while calculating the new available page length while attempting to allocate a page.

DXV101

The VMXDXV routine found a directory control statement that it did not recognize.

DXW001

An invalid XWKSECT was encountered.

DXW002

An invalid PFXSECT was found.

DXW003

An invalid POLSECT was found.

DXW100

A logic error occurred while updating a POOL member.

DXW101

A logic error occurred while compiling a directory entry.

DXW102

Attempted to allocate more than one page.

DXW103

An error occurred while writing a directory page.

DXW104

The POLSECT was not found in the profile chain.

DXW200

An error occurred while updating a directory POOL.

ECL001-ECL010

Contact Technical Support.

EDU100

An error occurred while expanding a source directory entry and its included directory PROFILE.

EDV100

An error occurred while expanding the POSIXGLIST.

EDV101

An error occurred while contracting the POSIXGLIST.

EDV102

An logic error occurred while processing continuation records.

EDV103

An logic error occurred while adding a new directory record after expanding a directory entry and its included directory PROFILE.

EIT001

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

EIT006

While processing an IUBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

EIT104

An error was returned from the IUCV RECEIVE function.

EIT105

An unexpected IUCV SEVER function was received from the ACI system service.

If this message appears at initialization, it may indicate that the Rules Facility was not generated properly. Either verify that the CP component installation was done properly, or, if you do not intend to run the Rules Facility, remove the ACCESS 1B4 RULE record from the PRODUCT CONFIG file. Then, start CA VM:Secure again. If the problem persists, contact Technical Support.

EIT106

Incoming data length is too large for the RECEIVE buffer.

EIT107

An unexpected error was received from an IUCV REJECT function for a heartbeat message from the CP component for availability check.

ELP001

An error occurred while encrypting a password.

ENC001-ENC002

Contact Technical Support.

END002

During system termination, CA VM:Secure found a routine on the termination exit chain with an invalid control block. If the abend recurs, contact Technical Support.

END003

Contact Technical Support.

EOP001-EOP003

Contact Technical Support.

ERD001-ERD009

Contact Technical Support.

ERF001

Contact Technical Support.

ERS001-ERS006

Contact Technical Support.

ETR001-ETR005
ETR008-ETR009

Contact Technical Support.

EVE001

While processing a PCBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

EVE002

The process being NUCPOSTed has already been terminated.

EWR001-EWR005
EWR008-EWR009

Contact Technical Support.

EXE001

An internal CA VM:Secure command, normally used only after initialization, was called before initialization completed. Enter ipl cms on the CA VM:Secure service virtual machine and start CA VM:Secure again.

EXE002

Unable to establish the SUBCOM environment.

EXE004

Contact Technical Support.

FDI001-FDI004
FDI006-FDI008

Contact Technical Support.

FMT001-FMT005

Contact Technical Support.

FPC001

Contact Technical Support.

FRF002

The CA VM:Secure service virtual machine needs more virtual storage to run. Define a larger virtual machine size by either using the CP DEFINE STORAGE command or by changing the CA VM:Secure directory entry. If you change the directory entry, log off the CA VM:Secure service virtual machine, then log on again.

FRF003

An event altered the contents of free storage on the CA VM:Secure service virtual machine. This condition has made it impossible for CA VM:Secure to satisfy a request for free storage because the pointers connecting the pages of free storage are no longer intact.

FRF004

The CA VM:Secure service virtual machine needs more virtual storage to run. Define a larger virtual machine size by either using the CP DEFINE STORAGE command or by changing the CA VM:Secure directory entry. If you change the directory entry, log off the CA VM:Secure service virtual machine, then log on again.

FRF006

An attempt was make to free a block of storage that is not aligned on a page boundary.

FRF007

An attempt was made to free a block of storage contained entirely within a single page. In doing so, either the page was found to be already free or the block was found to overlap two pages.

FRF008

While releasing pages of memory that were used in previous processes, CA VM:Secure was unable to locate a particular page that had been marked for release.

FRF009

CA VM:Secure was attempting to free storage and the amount of storage left in the storage pool was reduced to an invalid amount.

FRF010

A request for free storage was made before CA VM:Secure was fully initialized.

FRF011

A process requested 0 free storage. This is an invalid request.

FRF013

An attempt was made to return a block of storage that either is an invalid size or was never allocated. Storage at the end of the block may have been overlaid.

FRF016

When the PAGE subpool received a free–storage request, the amount of storage requested was not 4K bytes.

FRF017

When the PAGE subpool received a free–storage request, the address was not on a 4K boundary or the amount of storage requested was not 4K bytes.

FRF018-FRF019

Contact Technical Support.

FRG002

The CA VM:Secure service virtual machine needs more virtual storage to run. Define a larger virtual machine size by either using the CP DEFINE STORAGE command or by changing the CA VM:Secure directory entry. If you change the directory entry, log off the CA VM:Secure service virtual machine, then log on again.

FRG003

An event altered the contents of free storage on the CA VM:Secure service virtual machine. This condition has made it impossible for CA VM:Secure to satisfy a request for free storage because the pointers connecting the pages of free storage are no longer intact.

FRG004

The CA VM:Secure service virtual machine needs more virtual storage to run. Define a larger virtual machine size by either using the CP DEFINE STORAGE command or by changing the CA VM:Secure directory entry. If you change the directory entry, log off the CA VM:Secure service virtual machine, then log on again.

FRG006

An attempt was make to free a block of storage that is not aligned on a page boundary.

FRG007

An attempt was made to free a block of storage contained entirely within a single page. In doing so, either the page was found to be already free or the block was found to overlap two pages.

FRG009

CA VM:Secure was attempting to free storage and the amount of storage left in the storage pool was reduced to an invalid amount.

FRG010

A request for free storage was made before CA VM:Secure was fully initialized.

FRG011

A process requested 0 free storage. This is an invalid request.

FRG013

An attempt was made to return a block of storage that either is an invalid size or was never allocated. Storage at the end of the block may have been overlaid.

FRG015

Contact Technical Support.

FRG016

When the PAGE subpool received a free–storage request, the amount of storage requested was not 4K bytes.

FRG017

When the PAGE subpool received a free–storage request, the address was not on a 4K boundary or the amount of storage requested was not 4K bytes.

FRG018-FRG019

Contact Technical Support.

FRH002

The CA VM:Secure service virtual machine needs more virtual storage to run. Define a larger virtual machine size by either using the CP DEFINE STORAGE command or by changing the CA VM:Secure directory entry. If you change the directory entry, log off the CA VM:Secure service virtual machine, then log on again.

FRH003

An event altered the contents of free storage on the CA VM:Secure service virtual machine. This condition has made it impossible for CA VM:Secure to satisfy a request for free storage because the pointers connecting the pages of free storage are no longer intact.

FRH004

The CA VM:Secure service virtual machine needs more virtual storage to run. Define a larger virtual machine size by either using the CP DEFINE STORAGE command or by changing the CA VM:Secure directory entry. If you change the directory entry, log off the CA VM:Secure service virtual machine, then log on again.

FRH006

An attempt was make to free a block of storage that is not aligned on a page boundary.

FRH007

An attempt was made to free a block of storage contained entirely within a single page. In doing so, either the page was found to be already free or the block was found to overlap two pages.

FRH009

CA VM:Secure was attempting to free storage and the amount of storage left in the storage pool was reduced to an invalid amount.

FRH010

A request for free storage was made before CA VM:Secure was fully initialized.

FRH011

A process requested 0 free storage. This is an invalid request.

FRH013

An attempt was made to return a block of storage that either is an invalid size or was never allocated. Storage at the end of the block may have been overlaid.

FRH014-FRH015

Contact Technical Support.

FRH016

When the PAGE subpool received a free–storage request, the amount of storage requested was not 4K bytes.

FRH017

When the PAGE subpool received a free–storage request, the address was not on a 4K boundary or the amount of storage requested was not 4K bytes.

FRH018-FRH019

Contact Technical Support.

GLB100

An error occurred while updating the CA VM:Secure GLOBALS file.

GRO001

Unable to find the USRSECT for the issuer of the GROUP command.

HSH001

Contact Technical Support.

IOX001-IOX004

Contact Technical Support.

IPL001

Contact Technical Support.

IUC002

A CMSIUCV sever function failed for a process.

IUC003

A CMSIUCV accept function failed.

IUC004

Contact Technical Support.

IUC005

A CMSIUCV SEVER function failed attempting to reject a connection request.

IUC006-IUC007

Contact Technical Support.

IUM001-IUM002

Contact Technical Support.

IUP001

Attempted to connect to a product-to-product (PPI) resource a second time.

IUP002

Contact Technical Support.

IUP003

When CA VM:Secure received a request to send data to another CA product through the product-to-product interface (PPI), the amount of data exceeded the maximum buffer size.

IUP004

When CA VM:Secure received a request to send data to another CA product through the product-to-product interface (PPI), the parameter list was not aligned on a doubleword.

IUT001

Contact Technical Support.

LCK001

Process lock counter went negative.

LCK002

An I/O error occurred while processing the permanent lock file.

LCK003

A PERM lock was expected but not found.

LIN001

CA VM:Secure found an invalid LNKSECT or LNKSECT chain that was corrupted.

LIS101

The list handler program encountered a list that was greater than 4K.

LIS105

The list handler encountered a list with a header that was more than 4K.

LSA102

The list handler program encountered a recursive list that should have been caught in initial processing and that could cause a recursive call to VMXLSA.

LSA103

The list handler encountered a word in the list that requires an additional parameter, a situation that should have been caught in initial processing of the list.

LSA104

The list handler encountered a list that ended with a word that requires an additional parameter, a situation that should have been caught in initial processing of the list.

MAI001-MAI007

Contact Technical Support.

MAP001

While looking for a specific SUBSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP002

While looking for a specific VOLSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP003

While looking for a specific EXTSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP004

While looking for a specific DSKSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP005

While looking for a specific IGNSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP006

While looking for a specific SPESECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP007

While looking for a specific MGRSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP008

While looking for a specific DVCSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP009

While looking for a specific LNKSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP010

While looking for a specific USRSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP012

While processing DSKSECTs, at least one or a specific DSKSECT was expected but could not be found. This indicates either a logic problem or a storage overlay probably has occurred.

MAP014

While processing NOLSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

MAP015

An invalid offset into the record handler branch table was received. This indicates logic error probably has occurred.

MEA001

Contact Technical Support.

MNG001

While processing a SUBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

MNG002

A valid option on the MANAGER primitive could not be found in the internal table of kinds of data to stack.

MNG007

While processing a MGRSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

MNG102

While processing the internal mapping of minidisks, CA VM:Secure found too many subpools.

MON001-MON003

Contact Technical Support.

MSC001
MSC004

Contact Technical Support.

MSD001

An internal error occurred in one of the following primitives: SEMAPHORE, WAITSEC, WAITDATE, YIELD, or QLOCK.

MSG002

A request has been made to abend when a specific message is issued. This is defined on the MESSAGE record in the PRODUCT CONFIG file or using the DEBUG command.

MSG003

Contact Technical Support.

MSG004

During dynamic reconfiguration of the message facility the required reconfiguration control block was not found.

MSG005

Contact Technical Support.

MTX001-MTX005
MTX007-MTX013
MTX015-MTX016
MTX018

Contact Technical Support.

MUL001

Contact Technical Support.

OBT001

While looking for a specific SUBSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

OBT002

While looking for a specific VOLSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

OBT003

While looking for a specific EXTSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

OBT004

While looking for a specific DSKSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

OBT006

While looking for a specific SPESECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

OBT007

While looking for a specific MGRSECT, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

OBT011

While processing EXTSECTs, at least one or a specific EXTSECT was expected but could not be found. This indicates either a logic problem or a storage overlay probably has occurred.

OBT012

While processing DSKSECTs, at least one or a specific DSKSECT was expected but could not be found. This indicates either a logic problem or a storage overlay probably has occurred.

OBT101

The allocator’s MGRSECT was not found.

PAG009

Unable to swap directories due to repeated failure of DIAGNOSE X‘3C’.

PAG101

An entry point was called before page I/O was initialized.

PAG102

A logic–induced I/O error occurred.

PAG103

The primary UDIRBLOK page has no real UDIRBLOKs because there are no users in the directory.

PAG104

An attempt was made to write primary UDIRBLOK page at page 0.

PAG105

An attempt was made to write to a non–directory cylinder.

PAG106

An attempt was made to write before a Fixed–Block–Architecture (FBA) directory extent.

PAG107

An attempt was made to write beyond an FBA directory extent.

PAG108

On a system running on VM/ESA (370 Feature), the object directory was modified by a program other than CA VM:Secure.

PAG110

A process tried to release the object directory lock without first obtaining it.

PAK001-PAK002

Contact Technical Support.

PAT002

Contact Technical Support.

PFX002

An invalid PFXSECT was found.

PFX100

Attempted to add PFXSECT when one already exists.

PFX101

The profile reference chain is corrupted.

PGP001

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

PGP002

An invalid PGRP was found.

PGP003

An invalid DGRPM was found.

PGP100

An error occurred while editing the VMSECURE POSIX or VMDIRECT POSIX file.

PGP101

A logic error occurred when CA VM:Secure attempted to add a Gname twice.

PGP102

A logic error occurred while updating a DGRPM; a user was missing that had existed earlier.

POL002

While processing a POLSECT, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

PPI001

Attempted communication with an unknown service virtual machine.

PPI002

CA VM:Secure received an unsupported subcode from another CA product through the product-to-product interface (PPI).

PPI003

CA VM:Secure received an order with an incorrect amount of data from another CA product through the product-to-product interface (PPI).

PPI004

CA VM:Secure received an order to open a file from another CA product through the product-to-product interface (PPI), but the maximum number of files was already open.

PPI005

CA VM:Secure received an order to read or write from a file from another CA product through the product-to-product interface (PPI), but no file was open.

PPI006

CA VM:Secure received an order to read or write from a file from another CA product through the product-to-product interface (PPI), but the specified file was not open.

PRGxxx

A program check code, xxx, occurred.

PRO014
PRO016

Contact Technical Support.

PRS001

Contact Technical Support.

PRT001

Contact Technical Support.

PRT002

An error occurred when CA VM:Secure used the CP SPOOL command to spool a device to a user. An accompanying CP message is logged on the CA VM:Secure service virtual machine indicating why the CP SPOOL command failed. If the CP message does not provide sufficient information to correct the problem.

PSX001

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. A storage overlay might have occurred.

PUN001

Contact Technical Support.

PUN002

An error occurred when CA VM:Secure used the CP SPOOL command to spool a device to a user. An accompanying CP message is logged on the CA VM:Secure service virtual machine indicating why the CP SPOOL command failed. If the CP message does not provide sufficient information to correct the problem, contact Technical Support.

PUN003-PUN004

Contact Technical Support.

PXG003

CA VM:Secure called the program to read or write a page without passing the address of the Page Allocation Buffer control block. Save the dump and the CA VM:Secure console log and contact Technical Support.

PXG009

Unable to swap directories due to repeated failure of DIAGNOSE X‘3C’.

PXG010

The disk containing the current object directory has been replaced with an alternate one during CA VM:Secure operation.

PXG101

An entry point was called before Page I/O was initialized.

PXG102

A logic–induced I/O error occurred.

PXG103

The pointer to or the contents of the Buffered Page Control Structure (BPCS) has been corrupted.

PXG104

Unexpectedly found no pages buffered when a Buffered Page Control Structure (BPCS) exists.

PXG105

An attempt was made to write to a non–directory cylinder.

PXG107

There is an I/O error on the object directory device.

PXG108

On a system running on VM/ESA, the object directory was modified by a program other than CA VM:Secure.

PXG109

VMXPXG detected an invalid Buffered Page Control Structure (BPCS) processing function code.

PXG120

The PABSECT points to a page that contains invalid data.

PXG121

CA VM:Secure received an unexpected error during initialization while trying to read the object directory.

PXG122

The DDEV blocks in the object directory have a format that CA VM:Secure does not recognize.

PXG123

No existing user has a DDEV block.

RAM001-RAM007
RAM009

Contact Technical Support.

RC2001-RC2002

Contact Technical Support.

RC4001-RC4002

Contact Technical Support.

REB002

Unable to allocate directory space.

REB003

An error occurred reading a directory page.

REB004

An error occurred writing a directory page.

REB005

Unable to swap directories.

REB101

Unable to reset the directory space allocation.

REB102

A logic error was encountered allocating space on a directory page.

REB103

The object directory rebuilder encountered a UMACBLOK that pointed to a PRFSECT (directory profile control block) that didn’t exist.

REB104

Unexpected error code from EDIT OPEN while attempting to open a directory profile referenced by a UMACBLOK that was being processed.

REB110

During initialization, CA VM:Secure discovered ACIGROUP statements in directory entries, and the ACIGROUP was not defined on a GROUP record in the SECURITY CONFIG file.

REB112

A duplicate directory entry was found in the object directory.

REL001-REL002

Contact Technical Support.

REM001

While processing a DSDBLOK, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

REM002

While processing DSKSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

REM003

While processing VOLSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

REM004

While processing EXTSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

REM005

While processing VOLSECTs, at least one or a specific VOLSECT was expected but could not be found. This indicates either a logic problem or a storage overlay probably has occurred.

REM006

While processing IGNSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

REM007

While processing NOLSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

REM008

While processing LNKSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

REM009

While processing LNKSECTs on the undefined chain, one was found that did not point to its owning USRSECT. This indicates a logic error or storage overlay probably has occurred.

REM010

During the commit pass of the minidisk structure, an overlap condition was detected. This indicates a logic error probably has occurred.

REM011

While processing DSKSECTs, no more were found, indicating end of extent, but there should be more DSKSECTs. This indicates a logic error probably has occurred.

REM012

An invalid offset into the error message branch table was received. This indicates a logic error probably has occurred.

REM013

While processing DSKSECTs, at least one or a specific DSKSECT was expected but could not be found. This indicates either a logic problem or a storage overlay probably has occurred.

REM014

While processing a MGRSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

REM015

While processing a SUBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

REM016

While processing SUBSECTs, at least one or a specific SUBSECT was expected but could not be found. This indicates either a logic problem or a storage overlay probably occurred.

REP001-REP002

A directory update failed while processing the REPENTRY command.

RND001-RND002

Contact Technical Support.

RPL002-RPL005
RPL007

Contact Technical Support.

RPL008

CA VM:Secure received a request to register an outstanding reply, but no destinations were specified for the reply.

RSA001-RSA004

Contact Technical Support.

RUP001

Contact Technical Support.

RUP002

An attempt was made to initialize the interrupt handlers a second time.

RUP003

An unrecognized interrupt code was found while handling an interrupt.

RUP004

The CP SYSTEM RESTART command was entered by the operator on the server’s console.

RUP005

A Machine Check interrupt was sent to the virtual machine.

RUP007

An attempt to post the system CMS ECB failed because its address was zero.

RXB001

A bad SCB was passed.

RXB002

Unable to allocate directory space.

RXB003

An error occurred reading a directory page.

RXB005

Unable to swap directories.

RXB101

Unable to reset the directory space allocation.

RXB102

A logic error was encountered allocating space on a directory page.

RXB103

The object directory rebuilder encountered a DVMD that pointed to a PFXSECT (directory profile control block) that did not exist.

RXB104

Unexpected error code from EDIT OPEN while attempting to open a directory profile referenced by a DVMD that was being processed.

RXB106

CA VM:Secure could not find the page in the chain of page control blocks.

RXB108

A user ID was not found in the object directory.

RXB109

No users were found in the first user DUNDX page.

RXB110

During initialization, CA VM:Secure discovered ACIGROUP statements in directory entries, and the ACIGROUP was not defined on a GROUP record in the SECURITY CONFIG file.

RXB112

CA VM:Secure found a duplicate directory entry in the object directory.

RXB113

While rebuilding the internal LINK structure, a LNKSECT was found pointing to a USRSECT that does not exist. This indicates a logic error probably has occurred.

RXB114

The DVMD currently being processed does not have a valid eyecatcher field. A storage overlay or a logic problem has probably occurred.

RXB115

An invalid POSIX user ID index page was found.

RXB116

A logic error was found while processing POSIXGRP values.

RXB117

A corrupted POSIX user ID was detected.

RXC001

Internal support for issuing a CA VM:Secure message was not included in the VMXRXC CSECT.

RXF001-RXF002

Contact Technical Support.

RXS001

Contact Technical Support.

RXV001

While executing the REXXVARS primitive, CA VM:Secure could not locate an EXECCOMM SCBLOCK required by the primitive.

RXV002

An internal error occurred in the REXXVARS primitive.

RXV003-RXV005

Contact Technical Support.

SCN001

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

SCR003

An attempt to close a screen left open by the process at termination time failed.

SDC001-SDC002
SDC005

Contact Technical Support.

SDP003

Contact Technical Support.

SFS001

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

SFS002

While processing an SFPSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

SFS003

When searching for the desired storage group control block the required SFSPOOL block was not available.

SFS004

The anchor of SFSPOOL control blocks is zero when there should be a valid pointer.

SFS005

While processing an SFGSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

SFS006

While processing an MGRSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

SFS007

The SFGSECT returned from the routine to find it doesn’t have the correct storage group number. Probable logic error.

SFS100

CA VM:Secure tried to process an unsupported SFS function.

SHA001

Contact Technical Support.

SOP001

Contact Technical Support.

SRL001-SRL002

Contact Technical Support.

SSL001-SSL004

Contact Technical Support.

STK001

The CA VM:Secure service virtual machine needs more virtual storage to run. Define a larger virtual machine size by either using the CP DEFINE STORAGE command or by changing the CA VM:Secure directory entry. If you change the directory entry, log off the CA VM:Secure service virtual machine, then log on again.

STK002

CA VM:Secure received an error from the CMS CMSSTACK macro during a request to add a line to the CMS program stack.

STK003

An internal error occurred while CA VM:Secure tried to add a line to the CMS program stack.

STK004

While processing a DVCSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

STK101

An error occurred while converting the TOD clock.

STK102

CA VM:Secure invoked a routine called SYSSCAN which returned a token of all blanks instead of a nonzero return code.

STT001-STT004

Contact Technical Support.

SUR001

Contact Technical Support.

SUR002

CA VM:Secure is not authorized by the security system at your site to use the alternate user ID facility. Although CA VM:Secure was authorized at initialization, authorization has since been removed. Either give CA VM:Secure the proper authorization or change the configuration so that CA VM:Secure does not try to use the alternate user ID facility.

SUR003-SUR004

Contact Technical Support.

SUR005

CA VM:Secure was using your site’s security system when the security system became unavailable. Restart CA VM:Secure when the security system is available again.

SUR006-SUR010

Contact Technical Support.

SUT001-SUT002

Contact Technical Support.

SYS001

A routine exited with a damaged dynamic storage chain.

SYS002

CA VM:Secure received a request to call a routine, but the address was invalid.

SYT001-SYT008

Contact Technical Support.

TAB001-TAB002

Contact Technical Support.

TAP001-TAP006
TAP008-TAP009

Contact Technical Support.

TIC001-TIC003

Contact Technical Support.

TIE001-TIE002
TIE015

Contact Technical Support.

TIM001
TIM100
TIM101

Contact Technical Support.

TIO001-TIO002
TIO005-TIO007
TIO010
TIO012-TIO013

Contact Technical Support.

TIR001-TIR002
TIR009
TIR014

Contact Technical Support.

TIS001-TIS003

Contact Technical Support.

TIT001-TIT003

Contact Technical Support.

TRA001

An internal error occurred while processing macro trace output.

TRA002

Contact Technical Support.

TRK001-TRK003
TRK10-TRK013
TRK020
TRK022-TRK023

Contact Technical Support.

TRP002

While processing a PCBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

TRP003

The function requested to be trapped is unrecognized.

TRP004

The name of the previous function trapped is no longer valid. This probably indicates a storage overlay.

UEX001

Contact Technical Support.

UEX002

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

UEX003

While processing a CXTSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred. Or, the CXT indicates a file type other than TEXT or EXEC.

UEX004

The user exit is defined to be an EXEC, but the file loaded is not recognized as an EXEC.

UEX005

1. A post-user exit application exit routine was not defined.

2. An unexpected return code was received from the EXECLOAD routine.

3. File type of user exit to be loaded is not EXEC or TEXT.

UEX006

Contact Technical Support.

UEX100

While processing a UEXTBL entry, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

UEX101

While processing a SCB entry, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

UEX102

While processing a CXTSECT entry, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

UEX103

The definition of the user exit has been lost since the time it was invoked.

UEX104

While processing a PRDBLOK, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

UEX105

The user exit has ended abnormally and the definition of the user exit has been lost since the time it was invoked.

UPD001-UPD004

Contact Technical Support.

URI001

Contact Technical Support.

URI002

Someone may have detached or unreadied a virtual punch while a command was processing. Restart CA VM:Secure and enter the command again. If the problem recurs, contact Technical Support.

URI003

System spool space is full. When your system support staff has cleared some spool space, restart CA VM:Secure and enter the command again.

URI005

Contact Technical Support.

USE001

While processing an SCBSECT, the eyecatcher field of the control block was found to be invalid. This probably indicates that a storage overlay has occurred.

USE002

Contact Technical Support.

USE100
USE601
USE801

Contact Technical Support.

VMA001

While processing VOLSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

VMA002

While processing EXTSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

VMA003

While processing DSKSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

VMA004

While processing SUBSECTs, the eyecatcher field of the control block was found to be invalid. This indicates that a storage overlay probably has occurred.

WAI001

The number of seconds to wait on the WAITSEC primitive is greater than 2 weeks.

XLT001-XLT003

Contact Technical Support.

ZIO004
ZIO011-ZIO013

Contact Technical Support.

ZIP003
ZIP005-ZIP006
ZIP008-ZIO010
ZIP012

Contact Technical Support.