Batch Messages

Batch Messages

This chapter describes the Batch Messages.

A BACKUP FILE OF master-file-name WAS CREATED ON volser. FILE CONTAINS nnn MODULES.

Reason:

A master file was backed up. If you specified the volume serial number (volser) in the BACKUP DD statement, the volume serial number appears in this message. The message also reports the number of modules (nnn) the backup file contains.

Action:

No action required.

ABOVE STATEMENT -- INVALID. MODULE NAME NOT FOUND OR UNAUTHORIZED ACCESS.

Reason:

Either the module name was invalid or there was an illegal operation.

Action:

Contact your supervisor.

ABOVE STATEMENT IS INVALID IN A -REP ALL DATA STREAM.

Reason:

AllFusion CA‑Librarian updating control statements are not permitted in a -REP ALL data stream.

Action:

Review the input stream for errors and resubmit the job.

ABOVE STATEMENT SHOULD BE A -DLM, -SEL, -COPY, OR -INDEX.

Reason:

The module selection statement following an -OPT GPO statement is not a valid GPO command.

Action:

Correct the error and resubmit the job.

ABOVE STATEMENT SHOULD BE A -ADD, -SEL, OR -DLM CONTROL STATEMENT.

Reason:

A module selection command was expected, but not found. The input stream is flushed to the next valid -ADD, -SEL, or -DLM statement.

Action:

Inspect the Update Record Listing for a possible scrambled input deck.

ARCHIVE MODULE module-name CANNOT BE RESTORED TO THIS MASTER FILE.

Reason:

The named module is an archived module. The master file where it is being restored was not initialized to support archived modules.

Action:

Check with your systems programmer.

ARCHIVED MODULE CAN'T BE ADDED TO THIS MASTER FILE.

Reason:

You are trying to transfer an archived module from one master file to another.

The master file specified in the second step of the UTILITY -COPY operation was not initialized to support archived modules.

Action:

Add the module as a non-archived module or reinitialize the master file to support archiving.

ARCHIVING NOT PERMITTED ON THIS MASTER FILE.

Reason:

The ARC option is specified for a module on a master file that does not permit archived modules.

Action:

Contact your systems programmer.

ARE THERE OTHER LIBRARIAN JOBS ACTIVE BESIDES jobname. ANSWER YES OR NO.

Reason:

Another AllFusion CA‑Librarian job set the shared flag for the master file.

Action:

Check the console sheet to ensure that no other AllFusion CA‑Librarian jobs are active before replying NO.

Important! Do not respond NO if another AllFusion CA‑Librarian program is accessing the master file from the same or another CPU. If either LIB/OL or AllFusion CA‑Vollie is installed at your site, make certain that no one is executing the UPDATE command.

ASSUMING NO OFFSET OF PARAMETER NEAR POSITION.

Reason:

The compare string is enclosed in slashes (usually indicating an offset), but the string does not contain a valid offset. The entire string is used.

Action:

No action required.

A SYNTAX ERROR WAS DETECTED DURING EXPANSION OF A COPY STATEMENT REFERENCING MODULE module-name.

Reason:

A syntax error was detected during expansion of the named module.

Action:

Correct the error and resubmit the job.

AT LEAST ONE ERROR WAS FOUND THAT WAS NOT ASSOCIATED WITH A PARTICULAR MODULE NAME. ERROR IS IDENTIFIED IN UPDATE RECORD LISTING.

Reason:

The module selection command was expected, but not found. AllFusion CA‑Librarian ignores the statements.

Action:

Check the Update Record Listing for more information on the error.

ASSIGN FAILED FOR VOLUME xxxxxx

Reason:

The dynamic assign for the volume xxxxxx failed. The return code is from the VSE/ESA ASSIGN macro.

Action:

Check the $CCFGEN macro for the correct volser.

ATTEMPT TO ACCESS A PRINTER MODULE REJECTED.

Reason:

You cannot use -OPT COMPARE to compare the levels of a printer module.

Action:

No action required.

AUXFILE CANNOT BE CONCATENATED DATA SET.

Reason:

You cannot concatenate auxiliary input files.

Action:

Use consecutive -AUX statements.

AUXFILE ORGANIZATION MUST BE PS OR PO.

Reason:

The AllFusion CA‑Librarian -AUX facility does not support ISAM or VSAM file organization.

Action:

Specify a PS or PO data set.

BACKUP FILE ACCESS DENIED; INSUFFICIENT ACCESS AUTHORITY.

Reason:

You do not have the necessary authority to access the AllFusion CA‑Librarian backup file.

Action:

Contact your security administrator.

BACKUP FILE COULD NOT BE OPENED.

Reason:

The BACKUP DD statement is missing. All output to the backup tape is ignored.

Action:

Insert the BACKUP DD statement and request a backup tape.

BACKUP FILE DD STATEMENT SPECIFIED INVALID BLOCK SIZE. BLOCK SIZE HAS BEEN SET TO nnnn.

Reason:

You specified an invalid block size on the BACKUP DD statement. AllFusion CA‑Librarian automatically sets the block size value to the nearest correct value (nnnn) and resumes processing.

Action:

No action required.

BACKUP FILE IMPROPERLY ASSIGNED.

Reason:

The backup file was not assigned to a tape device. The execution is canceled.

Action:

Correct the error and resubmit the job.

BACKUP FILE RECORD SIZE MUST BE 8 LESS THAN THE CONTROL INTERVAL SIZE.

Reason:

The VSAM backup file assigned to ddname BACKUP during a disk-to-disk backup has an invalid record size specification.

Action:

Redefine the file and correct the record size specification.

BACKUP TAPE HAS INVALID FORMAT.

Reason:

The first block of the backup tape is invalid. The current execution is canceled.

Action:

Check that the correct backup tape was mounted before restoring the master file from an earlier backup tape.

BAD DATA RECORD IN MODULE module-name- SKIPPING CURRENT DATA BLOCKMODULE INCOMPLETE.

Reason:

AllFusion CA‑Librarian encountered an invalid data record in a module on the backup file being restored. The indicated module can be incomplete. In addition, other modules might be skipped.

Action:

Compare the current index listing with the previous index to determine what is missing. Recover from an alternate backup tape.

BASED ON SHOWCAT'S RETURN CODE, LIBRARIAN IS ASSUMING A 'BDAM' MASTER FILE. SHOWCAT RC=nn.

BASED ON SHOWCAT'S RETURN CODE, LIBRARIAN IS ASSUMING A 'BDAM' MASTER FILE. SHOWCAT RC=nn, VSAM CATALOG RC=nnn, VSAM CATALOG REASON CODE=nnn.

BASED ON SHOWCAT'S RETURN CODE, LIBRARIAN IS ASSUMING A 'BDAM' MASTER FILE. SHOWCAT RC=nn, VSAM ERROR CODE=nnn.

Reason:

Informational.

Action:

If the message is incorrect, See the applicable IBM guide for further information.

BLANK CONTROL STATEMENT.

Reason:

Columns 1 through 71 of the record read from SYSIN are blank. The z/OS and OS/390 Comparator (with condition code 16) performed no comparison.

Action:

Correct the control statement and resubmit the job.

CAPACITY OF THE REPLACING TABLE HAS BEEN EXCEEDED. REMAINDER OF COPY STATEMENT IGNORED.

Reason:

A COBOL COPY statement with a replacing clause contains more words, literals, or identifiers than can be stored in the word area.

Action:

If you cannot recode the statement to reduce the number of words to replace, use the compiler's COPY expansion facility.

CHANGING TO RESEQ OR NORESEQ NOT PERMITTED ON AN ARCHIE MODULE.

Reason:

You cannot change the option that controls the reassignment of sequence numbers after an update for an archived module.

Action:

No action required.

CLEAR OF LABEL AREA FAILED

Reason:

The label area CLRGRPL failed.

Action:

Contact Computer Associates Technical Support.

CONFLICT BETWEEN -AUX STATEMENT AND FILE ORGANIZATION. MODULE NOT ADDED TO MASTER.

Reason:

You are trying to add a partitioned data set as auxiliary input without specifying the member name.

Action:

See the Batch Command Reference Guide for the correct format.

CONTINUATION NOT FOUND.

Reason:

For the z/OS and OS/390 Comparator (condition code 16), the last nonblank character on the last record read from SYSIN was a comma. The Comparator expected, but did not find, an additional record.

For the VSE/ESA Comparator, the last nonblank character on the last record read from SYSIPT was a comma. The Comparator expected, but did not find, an additional record with the same Comparator control statement operation.

For either version of the Comparator, no comparison was performed.

Action:

Remove the extraneous comma or supply the continued record.

CONTROL RECORD ERROR DURING SPECIAL ADD USING -COPY UTILITY.

Reason:

In the second step of the UTILITY COPY procedure, the number and type of control records are checked while adding a module to the master file.

Action:

If there are not enough or the primary control record is not first, this message appears. Processing terminates for this ADD.

COPYDD EXPANSION SUPPRESSED: LOAD MODULE 'ADRDDC10' NOT ACCESSIBLE.

Reason:

The ADRDDC10 load module was not found in the load library specified in the STEPLIB DD statement or JOBLIB DD statement for an execution of LIB/DD.

Action:

Specify the correct load library on the STEPLIB or JOBLIB.

COPY STATEMENT CONTAINS TOO MANY STRINGS TO ANALYZE. EXPANSION SUPPRESSED.

Reason:

A COBOL COPY statement with a replacing clause contains too many words, literals, or identifiers for AllFusion CA‑Librarian to analyze.

Action:

Rewrite the statement reducing the level of complexity (if possible) or use the compiler's COPY expansion facility.

CUST ID NEEDED TO ASSIGN INITIAL CODE.

Reason:

To assign a MCD code to a master file, you must specify the customer identification on the -MCD statement.

Action:

See the Security Administration Guide for more information on assigning a MCD code.

CUST ID REQUIRED ON -MCD STATEMENT.

Reason:

To assign a MCD code to a master file, you must specify the customer identification on the -MCD statement.

Action:

See the Security Administration Guide for more information on assigning a MCD code.

DDNAME PARAMETER IN USE, DSN PARAMETER IS OMITTED.

Reason:

When you specify the DDNAME= parameter on the -JCL statement, the DSN= parameter is required.

Action:

Supply the DSN= parameter or remove the DDNAME= parameter.

DEFAULT MASTER FILE IS dsname ON UNIT cuu. ENTER COMMANDS.

Reason:

LIBFETCH found a valid default AllFusion CA‑Librarian master file.

Action:

You can issue the FILE subcommand to change this default or begin processing with either the SEL or INDEX subcommand.

DEVICE AT UNIT ADDRESS cuu NOT SUPPORTED BY LIBRARIAN.

Reason:

The device at the specified address was not a 3390, 3380, 3375, 3370, 3350, 3340, 3330, 3310, 2314, 2311, or a 2311 simulated on a 2314.

Action:

Specify a different unit address.

DISK MASTER FREE SPACE MAP CONTAINS INVALID DATA.

Reason:

The free space table is destroyed and the current execution is canceled.

Action:

Reinitialize and restore the master file.

-DLM STATEMENT FOLLOWED BY DATA RECORD(S).

Reason:

Data records cannot follow a -DLM (delete module) statement.

Action:

Correct the control stream.

DLM STATEMENT NOT FOLLOWED BY A -EMOD OR OTHER CONTROL STATEMENTS. MODULE NOT DELETED.

Reason:

The -DLM statement must not be followed by conflicting control statements referring to the module to delete (for example, -REP, -INS, and so on).

Action:

Resubmit with the -DLM statement followed by a -EMOD statement.

DSORG FOR THE JOBSTREAM FILE FOR GPO PROCESSING CAN NOT BE A PARTITIONED DATA SET

Reason:

You specified the jobstream file for a GPO execution as a partitioned data set.

Action:

Respecify as a sequential data set and resubmit the job.

DSORG FOR JOBSTREAM FILE CANT BE PDS FOR UTILITY OPT.

Reason:

You specified the jobstream file for a utility execution as a partitioned data set.

Action:

Respecify as a sequential data set and resubmit the job.

DUPLICATE VOLUME SERIAL NUMBER IN -VOL STATEMENT.

Reason:

The -VOL statement contained at least two identical volume serial numbers.

Action:

Correct the error and resubmit the job.

END OF GPO -- NO MODULE MET CRITERIA.

Reason:

No module on the master file met the criteria specified for the AllFusion CA‑Librarian Group Processing Option (GPO).

Action:

No action required.

END OF GPO. n MODULE(S) PASSED SELECTION CRITERIA.

Reason:

The indicated number of modules agree with the criteria specified by the GPO keywords used.

Action:

No action required.

ENDING SEQUENCE NUMBER NOT FOUND.

Reason:

There is an invalid sequence number in the -REP, -DEL, or -INC command. All updates for this module are bypassed.

Action:

Correct the error and resubmit the module update.

-END STATEMENT FOUND WITH MORE RECORD(S) BEHIND IT. RECORD(S) FOLLOWING -END BYPASSED.

Reason:

The -END statement was not the final statement for the input stream. AllFusion CA‑Librarian ignores statements that follow the -END statement.

Action:

Delete any records after the -END statement or move the -END statement to the end of the input stream.

ERROR CODE xxx ON SUCCESSFUL OPEN OF BACKUP FILE. PROCESSING CONTINUED.
ERROR CODE xxx ON SUCCESSFUL OPEN OF MASTER FILE. PROCESSING CONTINUED.
ERROR CODE xxx ON UNSUCCESSFUL OPEN OF BACKUP FILE. PROCESSING SUSPENDED.
ERROR CODE xxx ON UNSUCCESSFUL OPEN OF MASTER FILE. PROCESSING SUSPENDED.

Reason:

One of these messages appears when AllFusion CA‑Librarian receives an error indication from VSAM while trying to open the indicated file. The error code is decimal xxx.

Action:

For an explanation of the error code, see the applicable IBM guide.

ERROR DURING READING OF MASTER FILE. BACKUP IS INCOMPLETE.

Reason:

There was an irrecoverable I/O error during the reading of the disk master file for disk backup. The backup file is incomplete.

Action:

Recover lost modules through the selective restore (-COPY) feature of the UTILITY option.

ERROR DURING READING OF MASTER FILE. MODULE module-name SKIPPED.

Reason:

There was an irrecoverable I/O error during the reading of the disk master file for disk backup. The named module is not copied to the backup file.

Action:

Recreate the module from the previous backup file.

ERROR IN ABOVE STATEMENT. THE STATEMENT WAS IGNORED.

Reason:

A syntax error was found in the previous -EDIT, -SCAN, or -FILL statement. The operation is ignored.

Action:

Check for an invalid comma after the final string delimiter.

ERROR IN THIS STATEMENT.

Reason:

There is a COBOL syntax error.

Action:

A specific error message (see Chapter 11, "Syntax Checker Messages") follows this message.

FAIRMOD FAILURE, ERROR-CODE=.

Reason:

The error code is returned from FAIRMOD in register 16.

Action:

See the File Access Interface Routines Reference guide for additional information.

FAIRMOD FAILURE, RETURN-CODE=.

Reason:

The error return code is detected in FAIRMOD in the result area.

Action:

See the File Access Interface Routines Reference guide for additional information.

FAIROPN FAILURE, ERROR-CODE=.

Reason:

The error code is returned from FAIROPN in register 16.

Action:

See the File Access Interface Routines Reference guide for additional information.

FAIROPN FAILURE, RETURN-CODE=, REASON-CODE=.

Reason:

The error return code is detected in FAIROPN in the result area.

Action:

See the File Access Interface Routines Reference guide for additional information.

FAIRREC FAILURE, ERROR-CODE=.

Reason:

The error code is returned from FAIRREC in register 16.

Action:

See the File Access Interface Routines Reference guide for additional information.

FAIRREC FAILURE, RETURN-CODE=.

Reason:

The error return code is detected in FAIRREC in the result area.

Action:

See the File Access Interface Routines Reference guide for additional information.

FATAL ERROR FROM COPYDD: COPYDD TERMINATED.

Reason:

COPYDD processing terminates. Either CA-DataDictionary is inaccessible or the specified member is not found.

Action:

Verify that CA-DataDictionary is available or that the member exists.

FILE CONTAINS m MODULES OF WHICH n WILL BE DELETED DURING MASTER FILE RESTORATION.

Reason:

The disk master index is not in sequence and all modules that are out of sequence are not copied to the backup tape.

Action:

Reinitialize the new master file. Restore the backup tape created in this run and then selectively restore modules that were not copied from an earlier backup tape.

FINAL INPUT STATEMENT WAS NOT -END. MAKE SURE THAT LAST PART OF DECK WAS NOT DROPPED.

Reason:

An -END statement did not follow the data.

Action:

Make sure that the control stream is complete.

FIRST BLOCK OF MASTER FILE IS INVALID. IF NO ERROR IN ASSIGNMENT, FILE HAS BEEN DESTROYED.

Reason:

The first block of the master file contains invalid data. The current execution is canceled.

Action:

Reinitialize and restore the master file from the most recent backup tape.

FREE SPACE MAP CONTAINS INVALID DATA.

Reason:

Invalid data was found in the free space table. The table is destroyed.

Action:

Reinitialize the master file and restore from the backup tape.

GPO PROCESSING PROHIBITED FOR THIS MASTER FILE.

Reason:

The master file was initialized to inhibit the Group Processing Option and the GPO operand was found on the -OPT statement.

Action:

No action required.

HASH COUNTS INDICATE THAT THE CHANGES ABOVE ARE IDENTICAL TO THOSE OF PREVIOUS UPDATE FOR THIS MODULE. THE LIBRARIAN IS ASSUMING THIS IS AN ACCIDENTAL RERUN AND THE CHANGES HAVE NOT BEEN APPLIED. THIS CHECK MAY BE BYPASSED BY PLACING THE LETTER X IN COLUMN 7 OF THE -EMOD STATEMENT.

Reason:

AllFusion CA‑Librarian automatically protects against consecutive duplicate updates, a condition that occurs when you inadvertently resubmit an update that was already successfully applied. For each update to a module, AllFusion CA‑Librarian computes a hash count that it stores and then uses to determine if the update was submitted two consecutive times. Occasionally, different updates can also produce duplicate hash counts.

Action:

In either case, you can bypass the hash count check by coding an X in column 7 of the -EMOD control statement. If a -DATA statement precedes the -EMOD statement, you must place the X in the -DATA statement.

-HST STATEMENT(S) MUST FOLLOW -JCLT, -JCL, -LANG AND -PGMR STATEMENT(S).

Reason:

If you use -HST statements, they must follow -JCLT, -JCL, -LANG, and -PGMR statements.

Action:

Correct the error and resubmit the job.

IF DISK MASTER, 'DISK' OPERAND OMITTED ON -OPT STATEMENT.

Reason:

The input is incorrect for the file initialization execution.

Action:

Insert DISK on the -OPT statement for disk master initialization or include the -VOL statement for tape master initialization.

INCORRECT UNIT ASSIGNMENT FOR MASTER FILE.

Reason:

You must assign the master file to a 2311, 2314, 3330, 3340, 3350, 3375, 3380, 3390, or an FBA device.

Action:

If the unit assignment is correct, verify that AllFusion CA‑Librarian was generated to support the type of access method used (the ACCMETH= option of the LIBGEN installation macro can specify BDAM, VSAM, or both).

INCORRECT VERS OPERAND.

Reason:

The module version date and time are incorrect.

Action:

Verify that you are using the correct version for updating. If the module was not updated, specify VERS=0000.

INDEX CONTAINS INVALID DATA.

Reason:

Invalid data was found in the master file index. The file is destroyed.

Action:

Restore the master file from the most recent backup tape.

INDEX ENTRY OUT OF PLACE FOR MODULE module-name.

Reason:

The disk master index is not in sequence. All modules that are out of sequence are not copied to the backup tape.

Action:

Reinitialize the new master file. Restore the backup tape created in this execution and then selectively restore modules that were not copied from an earlier backup tape.

INIT DENIED; INSUFFICIENT ACCESS AUTHORITY.

Reason:

You do not have the necessary authority to initialize an AllFusion CA‑Librarian master file that is defined to your security system. Initialization minimally requires UPDATE and SCRATCH authorities.

Action:

Contact your security administrator.

INIT PROHIBITED; NO/INACTIVE SECURITY SYSTEM OR FILE UNDEFINED AS SECURITY SYSTEM RESOURCE.

Reason:

AllFusion CA‑Librarian master file initialization was prohibited because a security-related initialization parameter was specified, but one of the following conditions exist:

• There is no security system,
• Your security system is inactive, or
• The master file was not defined to your security system.

Action:

Contact your security administrator.

INITIALIZATION TERMINATED. CORRECT ERRORS, START OVER.

Reason:

Master file initialization failed.

Action:

Correct the errors specified and resubmit the job.

INPUT ERROR READING FREE SPACE MAP FOR INDEX LISTING.

Reason:

A system I/O error occurred. The master file free space table is destroyed.

Action:

Reinitialize the master file and restore from the backup tape.

INPUT ERROR READING INDEX FOR LISTING.

Reason:

A system I/O error occurred while reading the index. If a retry produces the same results, restore the master file from the most recent backup tape.

INPUT ERROR READING MODULE module-name FOR INDEX LISTING.

Reason:

A system I/O error occurred while reading the module control block.

Action:

If a retry produces the same results, selectively restore the module from a recent backup tape.

INPUT MODULE IS TOO LARGE TO PROCESS.

Reason:

The input module exceeds 255 blocks.

Action:

Use the UTILITY -INC option to split the module into several sections or reinitialize the master file with a larger block size.

INSUFFICIENT DISK SPACE FOR BACKUP FILE. BACKUP IS INCOMPLETE.

Reason:

Space allocation for disk backup was insufficient. The AllFusion CA‑Librarian execution is aborted.

Action:

If necessary, scratch the disk backup file. Assign more space to the backup file and resubmit the job.

INSUFFICIENT DISK SPACE TO ALLOCATE LIBAUDIT WORKFILE.

Reason:

Insufficient work space is left on the master file.

Action:

Enlarge the master file by using:

• The file copy facility (BKUPDISK).
• The current master file backup (BKUPTAPE), initializing a larger master file (INIT, DISK) and restoring the backup tape (RESTORE).

INSUFFICIENT MEMORY AVAILABLE.

Reason:

Insufficient memory available to execute AllFusion CA‑Librarian. The current execution is canceled.

Action:

Resubmit AllFusion CA‑Librarian in a larger partition.

INSUFFICIENT MEMORY AVAILABLE TO ACTIVATE LIBAUDIT PROCESSING.

Reason:

The current execution is terminated.

Action:

Resubmit AllFusion CA‑Librarian in a larger partition.

INSUFFICIENT SPACE ON MASTER FILE.

Reason:

Insufficient work space is left on the master file to process this module.

Action:

Enlarge the master file by using:

• The file copy facility (BKUPDISK).
• The current master file backup, initializing a larger master file and restoring the backup tape.

INVALID ATTEMPT TO ACCESS PRINTER MODULE.

Reason:

You cannot update, copy, or punch printer modules. All processing on the module is bypassed.

Action:

No action required.

INVALID -AUX STATEMENT -- BOOK NOT FOUND.

Reason:

The module the -AUX statement referenced is not added to the master file. The book name is not found in either system source library or in a private source library (if assigned).

The module is not added.

Action:

Verify that you spelled the book name correctly.

INVALID -AUX STATEMENT -- NO SOURCE LIBRARY ON SYSRES AND NO PRIVATE LIBRARY ASSIGNED.

Reason:

The module the -AUX statement referenced is not added to the master file.

Action:

Verify that you spelled the module name correctly.

INVALID CHARACTER IN SEQUENCE FIELD.

Reason:

At least one non-numeric character is in the sequence field and you specified SEQCHK or SEQUPD.

Action:

No action required.

INVALID CONTINUATION ERROR.

Reason:

During an execution of GPO, one or more of the following errors occurred:

• A GPO control statement ended in a comma or the logical operator ¬, &, or ;, but no GPO -CON statement followed.
• A GPO -CON statement followed a GPO control statement that did not end in either a comma or the logical operator ¬, &, or .
• The syntax of a GPO -CON statement was invalid.

Action:

Correct the error and resubmit the job.

INVALID CONTROL STATEMENT.

Reason:

The previous AllFusion CA‑Librarian control statement is invalid.

Action:

Correct the error and resubmit the update. Check for the omission of SEQUPD on the -SEL statement.

INVALID COPYDD STATEMENT -- UNMATCHED PARENTHESES.

Reason:

In the COPYDD statement, either the parentheses were incomplete or the parentheses were inappropriately paired.

Action:

Correct the error and resubmit the job.

INVALID DATA ENCOUNTERED IN MODULE module-name. MODULE INCOMPLETELY COPIED TO BACKUP TAPE.

Reason:

The named module is invalid. You must recreate it on the master file.

Action:

Restore the module from an earlier backup tape.

INVALID DATA ENCOUNTERED ON LIBAUDIT WORKFILE.

Reason:

Invalid data was found in the LIBAUDIT workfile.

Action:

Resubmit the job.

INVALID DATA FOUND IN INCLUDED MODULE module-name.

Reason:

Invalid data was found while decompressing the module included through -INC for execution.

Action:

Retry the operation. If it is still unsuccessful, selectively restore the included module from the backup tape.

INVALID DATA FOUND IN MODULE module-name.

Reason:

Invalid data was found while decompressing the module for listing or execution.

Action:

Retry the operation. If the module was destroyed, selectively restore the module from the backup tape.

INVALID GPO INDEX OPTION

Reason:

The first six characters of your GPO -INDEX or -INDEX(M) control statement were -INDEX, but the rest of the statement was invalid.

Action:

Correct the statement and resubmit the job.

INVALID GPO SYNTAX NEAR POSITION n

Reason:

There is an invalid GPO parameter, an invalid logical operator, or an invalid syntax of a logical operator occurred in the character string beginning at the nth position of a GPO statement.

Action:

Correct the statement and resubmit the job.

INVALID 'IN=' PARAMETER

Reason:

IN= specifies an invalid volume serial number. The current job is canceled. IN= must specify either a volume serial number that was previously specified at cycle initialization time or $$BKUP.

Action:

Correct the -OPT statement and resubmit the job.

INVALID INPUT MASTER FILE HAS BEEN MOUNTED.

Reason:

The z/OS and OS/390 MASTIN DD statement or the VSE/ESA SYS004 statement does not define an AllFusion CA‑Librarian tape master file.

Action:

Check your assignment for the file. It must define an AllFusion CA‑Librarian tape master file.

INVALID KEYWORD.

Reason:

You specified an invalid keyword on the -JCL statement.

Action:

Check the -JCL statement syntax.

INVALID MANAGEMENT CODE.

Reason:

You specified an incorrect management code on the -MCD statement.

Action:

Recalculate the management code and retry the operation. If necessary, See the Security Administration Guide for more information.

INVALID -MCD STATEMENT.

Reason:

No operands were present on the -MCD statement.

Action:

Remove the -MCD statement or add operands to it. If necessary, See the Security Administration Guide for more information.

INVALID OPERAND IN -OPT STATEMENT. - operand

Reason:

The indicated operand is invalid on a -OPT statement. The operand is the first or only operand AllFusion CA‑Librarian did not recognize.

Action:

Correct the error and resubmit the job.

INVALID OPERAND OR COMBINATION OF OPERANDS IN ABOVE STATEMENT. ALL OPERATIONS FOR THIS MODULE ARE BYPASSED.

Reason:

An invalid operand was found on an AllFusion CA‑Librarian control statement. TEMP, found on an -ADD statement or on a -SEL statement with COPY= or RENAME= specified, can be the cause of the error. This message is also issued when you specify the SYNCHK(l,a) operand on a system that was generated without the Syntax Checker capability. The module is not processed.

Action:

Correct the error and resubmit the job.

INVALID PARM FIELD OPERAND ON 'EXEC' STATEMENT.

Reason:

An invalid operand was found in the PARM field of the EXEC statement.

Action:

Correct the error and resubmit the job.

INVALID -SCAN STATEMENT.

Reason:

The global scan statement is invalid. The execution is aborted. There is probably an invalid delimiter or a comma after the delimiter.

Action:

Correct the error and resubmit the job.

INVALID SEQ PARAMETER. ALL OPERATIONS FOR THIS MODULE ARE BYPASSED.

Reason:

Sequence specifications are incorrect. The module is not processed.

Action:

Correct the error and resubmit the job.

INVALID SEQUENCE NUMBER LENGTH SPECIFIED. LENGTH=6 USED.

Reason:

You specified the SEQ= option with an invalid length. If the starting value is 81, then the length must be 6. If the starting value is not 81, then the sum of the starting column and length must not exceed 81. The module is processed with a sequence length of 6.

Action:

Correct the error and resubmit the job.

INVALID SEQUENCE PARAMETERS FOR SEQCHK OPERAND.

Reason:

The SEQCHK= operand specified invalid parameters.

Action:

Correct the error and resubmit the input for this module. SEQCHK= does not support external sequencing.

INVALID SEQUENCE PARAMETERS FOR SEQUPD OPERAND.

Reason:

The module is externally sequenced and, therefore, cannot be updated using the SEQUPD option.

Action:

No action required.

I/O ERROR READING BLOCK 1 OF MASTER FILE.

Reason:

An I/O error occurred during COSS processing. This message can occur when:

• A non-AllFusion CA‑Librarian data set is specified for MASTER.
• The master file is not initialized.
• The master file was corrupted and has invalid data in block one.

Action:

Verify that the file is a properly initialized AllFusion CA‑Librarian master file. If so, the master file can be corrupted. Contact Computer Associates Technical Support.

I/O ERROR DURING WRITING OF BACKUP. FILE NOT BACKED UP.

Reason:

There was an irrecoverable I/O error on a disk backup file. The execution is aborted.

Action:

Scratch the backup file, if necessary, and resubmit the job. If the error message reoccurs, reassign the backup file to a different disk device.

I/O ERROR ON -AUX FILE.

Reason:

There was an error when opening or reading the sequential -AUX file.

Action:

Check the DD statement for a valid block size and data set name.

I/O ERROR ON DISK MASTER WHEN READING BLOCK 0.

Reason:

There is a system I/O error that destroyed the master file.

Action:

Reinitialize the master file and restore from the most recent backup tape.

I/O ERROR ON WORK FILE.

Reason:

A system I/O error occurred on one of the AllFusion CA‑Librarian work files.

Action:

Resubmit the job. If it is still unsuccessful, reassign the work files to another area.

I/O ERROR WHEN TRYING TO SET SHARED FLAG ON DISK MASTER.

Reason:

There is a system I/O error that destroyed the master file.

Action:

Recreate the master file from the most recent backup tape.

I/O ERROR WHILE READING MASTER FILE INDEX.

Reason:

An I/O error occurred when GPO was reading the master file index.

Action:

Recreate the master file from the most recent backup tape.

I/P MASTER BLOCKSIZE INFORMATION MISSING.

Reason:

You did not specify block size DCB information for an unlabeled input tape master.

Action:

Resubmit the job, specifying the DCB BLKSIZE subparameter.

I/P MASTER CANNOT BE OPENED. CHECK DD STATEMENT.

Reason:

An error occurred while opening the input or output master file.

Action:

Check for a missing MASTIN statement and resubmit the job.

I/P TAPE MASTER IMPROPERLY ASSIGNED.

Reason:

The input tape master file is not assigned to a tape device. The execution is canceled.

Action:

Assign the input tape master file to a tape device.

IRRECOVERABLE I/P ERROR ON LIBAUDIT WORKFILE.

Reason:

A system input error occurred while reading the LIBAUDIT workfile.

Action:

Reapply the update.

IRRECOVERABLE INPUT ERROR ON DISK MASTER FREE SPACE MAP.

Reason:

A system I/O error occurred. The master file free space table is destroyed.

Action:

Using a backup tape, reinitialize the master file and restore from the backup

tape.

IRRECOVERABLE INPUT ERROR ON DISK MASTER INDEX.

Reason:

A system I/O error occurred while reading the master file index block.

Action:

Restore the master file from a backup tape if a retry produces the same results.

IRRECOVERABLE INPUT ERROR ON DISK MASTER INDEX, BACKUP TAPE IS NOT REUSABLE.

Reason:

A system I/O error occurred while reading the index. The current execution is canceled.

Action:

Restore the master file from the previous backup tape. Do not use the backup tape created in the current execution.

IRRECOVERABLE INPUT ERROR ON INCLUDED MODULE module-name.

Reason:

A system I/O error occurred while reading the module for execution. The module

is not completely included in the job stream. The run continues.

Action:

Selectively restore the module from a backup tape if a retry produces the same result.

IRRECOVERABLE INPUT ERROR ON MODULE module-name.

Reason:

A system I/O error occurred while reading the specified module.

Action:

If a retry produces the same results, selectively restore the module from a current backup tape. The module is not updated and processing continues with the next module.

IRRECOVERABLE INPUT ERROR ON MODULE module-name, HEADER BUT NO DATA COPIED TO BACKUP TAPE.

Reason:

There is a system I/O error on the named module.

Action:

Recreate the module on the master file.

IRRECOVERABLE INPUT ERROR ON MODULE module-name, MODULE NOT COPIED TO BACKUP TAPE.

Reason:

There is a system I/O error on the named module.

Action:

Recreate the module on the master file.

IRRECOVERABLE O/P ERROR ON LIBAUDIT WORKFILE.

Reason:

A system output error occurred while writing the LIBAUDIT workfile.

Action:

Reapply the update.

IRRECOVERABLE OUTPUT ERROR ON DISK MASTER. FILE HAS BEEN DESTROYED.

Reason:

The current execution is canceled.

Action:

Reinitialize and restore the master file from the most recent backup tape.

IRRECOVERABLE OUTPUT ERROR ON DISK MASTER FREE SPACE MAP.

Reason:

A system I/O error occurred. The master file free space table is destroyed.

Action:

Reinitialize the master file and restore from the most recent backup tape.

IRRECOVERABLE OUTPUT ERROR ON DISK MASTER INDEX.

Reason:

A system I/O error occurred while writing the master file index block.

Action:

Reinitialize and restore the master file from a backup tape.

IRRECOVERABLE OUTPUT ERROR ON FIRST BLOCK OF DISK MASTER.

Reason:

A system I/O error occurred canceling the current execution and destroying the master file.

Action:

Reinitialize and restore the master file from the most recent backup tape.

IRRECOVERABLE OUTPUT ERROR ON MASTER CONTROL BLOCK.

Reason:

A system I/O error occurred while writing the first block of the disk master file. The current execution is canceled.

Action:

Reinitialize the master file and restore from the most recent backup tape.

IRRECOVERABLE OUTPUT ERROR ON MODULE module-name.

Reason:

A system I/O error occurred while processing the module. The module named is not updated. Processing continues with the next module.

Action:

If a retry produces the same results, use the backup for the current master file and restore.

routine IS THE NAME OF THE I/P (or O/P) EXIT ROUTINE REQUIRED BY THIS MASTER FILE.

Reason:

The master file was initialized to require an input (or output) exit when processing. No such exit was named in the EXEC statement.

Action:

Insert the required routine name and resubmit the job.

JCL, LANG, OR PGMR PARAMETER HAS INVALID LENGTH.

Reason:

The parameter specified on a -JCL, -LANG, or -PGMR statement is too long.

See the Batch Command Reference Guide for descriptions of these parameters.

Action:

Correct the invalid parameter and resubmit the updates for the module.

JOBSTREAM FILE UNASSIGNED. OUTPUT TO THIS FILE (IF ANY) SUPPRESSED.

Reason:

SYS008 or its equivalent logical unit (specified in LIBGEN) is unassigned for this execution. All output to this file is ignored.

Action:

Assign the jobstream file and resubmit the job.

JOBSTREAM OVERFLOW ON MODULE module-name. ALL SUBSEQUENT OUTPUT FOR THIS FILE FLUSHED.

Reason:

Jobstream file is too small.

Action:

Enlarge the file by making extents larger.

LABEL ADD FAILED FOR DTFNAME nnnnnnn.

Reason:

Dynamic ADDLBL for file nnnnnnn failed.

Action:

Contact Computer Associates Technical Support.

LIBAUDIT PROCESSING SUPPRESSED; LOAD MODULE CPRT1M NOT ACCESSIBLE.

Reason:

The LIBAUDIT load module/phase was not found.

Action:

See the Installation Guide or CA Librarian VSE/ESA Installation Guide for instructions on link editing CPRT1M.

LIBRARIAN JOB jobname UNABLE TO ENQUEUE 'VSAM' DISK MASTER FILE. ENQUEUE WILL BE REISSUED AT 16 SECOND INTERVALS.

Reason:

Another job has the master file enqueued. When this job completes, the specified AllFusion CA‑Librarian job proceeds to enqueue.

Action:

No action required.

LIMIT ON NUMBER OF MODULES PER RUN HAS BEEN EXCEEDED. INPUT FOR MODULE module-name AND ALL MODULES FOLLOWING IT IN THE INPUT STREAM WILL BE IGNORED.

Reason:

You can only process 500 modules in a single tape master execution.

Action:

Include the module named and all the succeeding modules in another update execution. You can process more than 500 modules by submitting all control statements in ascending alphanumeric order and executing AllFusion CA‑Librarian with the NOSORT option specified.

LOGICAL ERROR: PUT REQUEST ERROR CODE IS xxx.

Reason:

AllFusion CA‑Librarian received an error indication from VSAM while trying to update a control interval through a request macro.

Action:

Register 16 contains an X'08' and the error code is decimal xxx. For an explanation of the error code, see the applicable IBM guide.

MASTER FILE ACCESS DENIED; INSUFFICIENT ACCESS AUTHORITY.

Reason:

You do not have the necessary authority to access a master file that is defined to your security system.

Action:

Contact your security administrator.

MASTER FILE ACCESS PROHIBITED; SECURITY SYSTEM INACTIVE.

Reason:

Access to an AllFusion CA‑Librarian master file was prohibited because the master file was initialized with SAFLOCK=YES and your security system is inactive.

Action:

Rerun the job when the security system becomes active.

MASTER FILE ALLOCATION IS TOO SMALL.

Reason:

The master file allocation must be at least 5 blocks.

Action:

Resubmit the initialization step, increasing the space assignment for the master file.

MASTER FILE ALREADY CONTAINS A MODULE NAMED module-name.

Reason:

The module named on the -ADD statement or in a COPY or RENAME operand is already on the master file.

Action:

Check the listings for a possible rerun of the job.

MASTER FILE AND BACKUP DSNAME'S CANNOT BE EQUAL.

Reason:

The disk backup data set name and the disk master data set name cannot be the same.

Action:

Create a copy of the master file under a different name and use IEHPROGM to rename (catalog) it.

MASTER FILE BACKUP SKIPPED nnn MODULES.

Reason:

The disk master index is not in sequence. All modules that are out of sequence are not copied to the backup tape.

Action:

Reinitialize the new master file. Restore the backup tape created in this run. Then selectively restore modules that were not copied from an earlier backup tape.

MASTER FILE CANNOT BE RESTORED BECAUSE IT HAS BEEN ACCESSED SINCE ITS INITIALIZATION.

Reason:

The master file was not reinitialized. The current execution is canceled.

Action:

Check for a possible destruction of a valid master file before reinitializing. Initialize a new master file before attempting the restore operation.

MASTER FILE DD STATEMENT MISSING.

Reason:

The -OPT statement specifies a disk master to initialize, however, no MASTER DD statement is provided.

Action:

Insert the MASTER DD statement and resubmit the initialization step.

MASTER FILE DD STATEMENT SPECIFIES INVALID BLOCK SIZE. BLOCK SIZE HAS BEEN SET TO nnn.

Reason:

The block size specified is not valid for the device. The block size is automatically set to the closest valid block size for the device and processing continues.

Action:

No action is required. The System Services Reference Guide contains a chart of valid block sizes for each supported device.

MASTER FILE FORMAT IS OBSOLETE TO THIS VERSION OF LIBRARIAN. SEE CONVERSION INSTRUCTIONS.

Reason:

The master file was initialized under an obsolete version of AllFusion CA‑Librarian.

Action:

Contact Computer Associates Technical Support for conversion instructions.

MASTER FILE INITIALIZATION RUN SPECIFIES INVALID BLOCK SIZE. BLOCK SIZE HAS BEEN SET TO nnn.

Reason:

You specified an incorrect block size on the -OPT statement. The block size is automatically set to the closest valid value and processing continues.

Action:

No action is required.

MASTER FILE IS NOT ON A SUPPORTED DEVICE.

Reason:

The AllFusion CA‑Librarian master file was not assigned to an acceptable device type.

Action:

Resubmit the initialization with the master file assigned to a support device

type. See the System Services Reference Guide for supported device types.

MASTER FILETYPE ERROR - n.

Reason:

You identified the master with an invalid file organization. Only VSAM and

BDAM are valid.

Action:

Correct the filetype.

MASTER FILE RECORD SIZE MUST BE 8 LESS THAN CONTROL INTERVAL SIZE.

Reason:

The record size is not eight less than the CISIZE for the VSAM master file.

Action:

Redefine the VSAM master file and correct the record size specification.

MASTER FILE REINITIALIZATION IS COMPLETE.

Reason:

The AllFusion CA‑Librarian master file reinitialization function completed normally.

Action:

No action required.

MASTER FILE WAS CREATED BY A MORE RECENT VERSION OF LIBRARIAN THAN THE ONE BEING EXECUTED.

Reason:

You are executing an obsolete version of AllFusion CA‑Librarian.

Action:

Call Computer Associates Technical Support for conversion instructions.

MASTER VOLUME ERROR - xxxxxx.

Reason:

An error occurred while trying to access the master on volume xxxxxx. The return code is from the VSE/ESA GETVCE macro.

Action:

Contact your systems programmer.

'MASTOUT' DD STATEMENT MISSING.

Reason:

You did not specify a MASTOUT DD statement or NOOUTPUT on the -OPT statement.

Action:

Insert a MASTOUT DD statement and resubmit the job.

MAXIMUM NUMBER OF LEVELS EXCEEDED, OLDEST LEVEL CLEARED. nn LEVELS.

Reason:

The archived module reached the maximum number of levels that can be maintained. AllFusion CA‑Librarian clears the oldest level of the module so that a new level can be created for this update. This message can also be issued when a module is transferred from one archived master file to another through the -COPY statement, and the maximum number of levels supported on the receiving master file is less than the number of levels currently maintained for the module.

AllFusion CA‑Librarian adds the module, but clears the specified number of oldest levels of the module.

Action:

No action required.

-MCD CARD SUCCESSFULLY PROCESSED BUT MANAGEMENT CODE HAS NOT BEEN CHANGED.

Reason:

You cannot change the base code during utility or GPO processing.

Action:

To change the management code, resubmit a non-utility or non-GPO execution of AllFusion CA‑Librarian.

-MCD CARD WRITTEN TO JOBSTREAM FILE.

Reason:

The -MCD statement was written to the job stream file during utility or GPO processing.

Action:

No action required.

MEMBER member-name NOT FOUND.

Reason:

The -AUX statement specified a non-existent member of a PDS.

Action:

Correct the error and resubmit the statement.

MISSING OR INVALID OPERAND FIELD.

Reason:

You did not specify criteria parameters on a GPO command statement.

Action:

Insert at least one operand on a GPO -SEL, -DLM, -COPY, or -INDEX command and resubmit the job.

MODULE NOT ADDED TO MASTER, SEQUENCE NUMBER ERROR.

Reason:

The -ADD statement specified the SEQCHK= option. At least one sequence error was encountered.

Action:

Correct the error and resubmit the job.

MODULE NOT ON MASTER FILE.

Reason:

The module specified on the AllFusion CA‑Librarian control statement was not found.

Action:

Verify that the module exists on the specified master file. Verify the module and master file. Correct errors and resubmit the job.

MODULE TO BE REPLACED HAS BEEN DELETED, IF PRESENT.

Reason:

The -ADD in the second step of this UTILITY -COPY failed. If a module of the same name existed on the master file before the -ADD was attempted, it was deleted.

Action:

If this message accompanies the message OUTPUT MODULE TOO LARGE TO PROCESS, backup the master file, reinitialize it with a larger block size, and restore it from the backup tape. When this is done, rerun the -ADD step to complete the -COPY.

MODULE module-name REPLACED ON MASTER. PASSWORD IS password.

Reason:

The specified module was replaced on the master file through the -COPY facility.

Action:

No action required.

MODULE UPDATE BYPASSED DUE TO CONDITIONAL PARAMETER. A PRIOR UPDATE HAS FAILED.

Reason:

The module update depended on the successful completion of all previous updates, and one of the previous updates failed. The module was not updated.

Action:

Correct the failing update and resubmit the job.

MODULE module-name WAS NOT RESTORED; EXCEEDED MAXIMUM OF 255 BLOCKS DURING RESTORATION.

Reason:

The module would exceed 255 blocks on the receiving master file.

Action:

Resolve by:

• Reinitializing the master file with a larger block size and rerun the restoration job, or
• Selectively restoring the offending module through UTILITY -COPY to a master file with a larger block size.

MORE THAN ONE MILLION RECORDS IN THE I/P MODULE: LIBAUDIT PROCESSING TERMINATED.

Reason:

LIBAUDIT cannot process a module with more than 1,000,000 records.

Action:

Resolve by:

• Splitting your module into two or more smaller modules and resubmit for LIBAUDIT processing, or
• Updating using batch AllFusion CA‑Librarian with REP ALL,NOAUDIT.

MORE THAN ONE MILLION RECORDS IN THE SYSIN FILE; LIBAUDIT PROCESSING TERMINATED.

Reason:

LIBAUDIT processing is limited to one million records.

Action:

Resolve by:

• Updating using batch AllFusion CA‑Librarian with REP ALL,NOAUDIT, or
• Splitting your module into two or more updates.

MORE THAN 30 VALID -SCAN STATEMENTS HAVE BEEN READ. ONLY THE FIRST 30 WILL BE PROCESSED.

Reason:

The maximum number of -SCAN statements for a global scan was exceeded. The current execution processes the first 30 statements.

Action:

Resubmit the job with the unprocessed -SCAN statements.

MOST RECENT LEVEL REPLACED DUE TO NOARC STATUS.

Reason:

The NOARC option, in effect for this archived module, replaced the current level of the module with the level this update created. All other levels of the module are retained.

Action:

No action required.

MUTUALLY EXCLUSIVE OPERANDS PRESENT.

Reason:

You used an invalid combination of the SYNCHK(l,a) option with either the CCOPY or CCOPYOFF option.

Action:

Remove one of the operands and resubmit the job.

NEITHER TAPE NOR DISK MASTER FILE ASSIGNED.

Reason:

No master file was defined in the JCL. The execution is canceled.

Action:

Assign a tape or disk master file.

NO/nn ADDITIONAL LEVEL(S) MAY BE ARCHIVED FOR THIS MODULE.

Reason:

The archived module is within ten archiving levels of the maximum number that the master file supports for its modules. The number of additional levels that can be archived for the module before the oldest level is cleared is reported in this message as NO or the value n.

Action:

No action required.

NO DATA RECORD(S) FOR THIS MODULE.

Reason:

No source statements followed the -ADD control statement. The module was not added.

Action:

Supply data records and resubmit the job.

NO DD PROVIDED FOR EITHER TAPE OR DISK MASTER FILE.

Reason:

No tape or disk master file was assigned. The AllFusion CA‑Librarian run is canceled.

Action:

Insert the correct DD statement and resubmit the job.

NO GPO SELECTION CRITERIA SPECIFIED.

Reason:

Either you omitted the keywords on a GPO control statement or you supplied a non-recognizable GPO control statement after an -OPT GPO statement.

Action:

Correct the problem and resubmit the job.

NO MODULES FOUND FOR REQUESTED INDEX.

Reason:

No modules on the master file satisfy the requested specifications for the index listing.

Action:

Check to ensure that the programmer name is valid and that the master file is not empty.

NO OPERANDS IN ABOVE STATEMENT.

Reason:

You did not specify any operands on the -JCL statement.

Action:

Specify at least one operand.

NO RECORDS IN JOBSTREAM FILE.

Reason:

There are no records in the jobstream file.

Action:

Specify at least one record in the jobstream file.

NO SOURCE RECORD(S) AFTER -INS OR -REP STATEMENT.

Reason:

The required data statements do not follow an -INS or -REP statement.

Action:

Correct the error and resubmit the update.

NO VALID EDIT/SCAN/FILL REQUESTS FOUND.

Reason:

No valid -EDIT, -SCAN, or -FILL statements were found and no operations were performed.

Action:

Correct the errors and resubmit the update.

NO VALID RECORDS IN AUXFILE.

Reason:

The -AUX data set is empty. The module is not added or updated. AllFusion CA‑Librarian checks the final block pointer in the format DSCB. Data sets created under VSE/ESA have an incorrect final block pointer.

Action:

You can use IEBGENER to duplicate the data set. You can then use the duplicate as input.

NOOUTPUT SPECIFIED WHEN THERE IS NO I/P MASTER.

Reason:

The -OPT statement contains both the NOOUTPUT and NOINPUT operands.

Action:

Correct the -OPT statement and resubmit the job.

OPEN FOR INDEX FILE UNSUCCESSFUL. INDEX LISTING SUPPRESSED.

Reason:

You did not specify an INDEX DD statement. The INDEX option is ignored.

Action:

No action required.

OPEN FOR LIST FILE UNSUCCESSFUL. LISTING SUPPRESSED.

Reason:

You did not specify a LIST DD statement. The LIST option is ignored.

Action:

No action required.

OPEN FOR SYSPUNCH FILE UNSUCCESSFUL. PUNCH SUPPRESSED.

Reason:

You did not specify a SYSPUNCH DD statement. The PUNCH option is ignored.

Action:

No action required.

OPERAND 'operand' SHOULD BE FIRST OPERAND ON FIRST -OPT STATEMENT.

Reason:

Self-explanatory.

Action:

Correct the error and rerun the job. Possible initial operands are: UTILITY, GPO, INIT, XREF, and COMPARE.

OPERATOR REPLY INDICATES THAT THERE IS NO SIMULTANEOUS EXECUTION OF THE LIBRARIAN. THE SHARED FLAG HAS BEEN RESET BY THE OPERATOR.

Reason:

The operator reset the shared flag that indicates possible concurrent executions of AllFusion CA‑Librarian.

Action:

No action required.

O/P MASTER BLOCKSIZE INFORMATION MISSING.

Reason:

You must specify the DCB BLKSIZE subparameter on the MASTOUT DD statement.

Action:

Supply the DCB BLKSIZE subparameter and resubmit the job.

O/P MASTER CANNOT BE OPENED.

Reason:

The MASTOUT DD statement is either invalid or missing.

Action:

Correct the DD statement or, if an output master is not wanted, put NOOUTPUT on the -OPT statement.

O/P MASTER CANNOT BE OPENED. CHECK DD STATEMENT.

Reason:

An error occurred while opening the input or output master file.

Action:

Check for a missing MASTOUT DD statement and rerun the job.

O/P MODULE HAS EXCEEDED 255 DISK BLOCKS.

Reason:

The module exceeds 255 blocks.

Action:

Use the UTILITY option to split the module into several sections or reinitialize the master file with a larger block size.

O/P TAPE MASTER IMPROPERLY ASSIGNED.

Reason:

The output tape master file is not assigned to a tape device. The execution is canceled.

Action:

Assign the output tape master to a tape device.

OSJOB DATA SET COULD NOT BE FOUND BY OBTAIN.

Reason:

OSJOB defined an old data set that did not exist. The current execution is canceled.

Action:

Reassign OSJOB and resubmit the job.

OSJOB DD STATEMENT MISSING.

Reason:

You did not specify a OSJOB DD statement. The current execution is canceled.

Action:

Insert the OSJOB DD statement and resubmit the job.

OSJOB DD STATEMENT SPECIFIES UNACCEPTABLE UNIT.

Reason:

OSJOB DD statement must reference a disk or tape unit. The current execution is canceled.

Action:

Reassign the OSJOB DD statement and resubmit the job.

OUTPUT MODULE IS TOO LARGE TO PROCESS.

Reason:

The module exceeds 255 blocks.

Action:

Use the UTILITY -INC option to split the module into several sections or reinitialize the master file with a larger block size.

OVERFLOW -- STATEMENT NOT ALTERED.

Reason:

The -EDIT operation was not performed on the indicated statement since valid characters are forced past the ending justification column.

Action:

Review the -EDIT statement to determine whether to correct the -EDIT statement and resubmit the job.

PHASE phase-name IS NOT IN CORE IMAGE LIBRARY.

Reason:

The indicated AllFusion CA‑Librarian phase is not found in the core image library. Either there was an error in the generation of AllFusion CA‑Librarian or the phase was deleted.

Action:

Place the phase in the core image library and rerun the job.

PHASE phase-name IS IN THE SVA.

Reason:

The indicated AllFusion CA‑Librarian phase must not be in the SVA, but it was found there.

Action:

Remove the phase from the SVA and rerun the job.

PHYSICAL ERROR: PUT REQUEST CODE IS xxx.

Reason:

AllFusion CA‑Librarian received an error code indication from VSAM while trying to update a control interval through a request macro. Register 16 contains an X'0C' and the error code is decimal xxx.

Action:

For an explanation of the error code, see the applicable IBM guide.

PREMATURE END-FILE ON I/P MASTER.

Reason:

The input tape master file was destroyed.

Action:

Recreate it from a backup tape.

Note: You must precede VSE/ESA tape master files with a tape mark and it must be the first file on the tape.

PREMATURE END-FILE ON O/P MASTER.

Reason:

The AllFusion CA‑Librarian tape master internal label is missing.

Action:

Rerun with OUT=NL on the -OPT statement.

PROCESSING OF ARCOFF OPTION HAS FAILED.

Reason:

The tape master file being processed was not initialized to support archived modules. The module update where you specified the ARCOFF option failed and, therefore, the ARCOFF is not processed. Because the ARCOFF was not processed, the module is still an archived module and cannot be written to the output tape. The execution is terminated. The cycle file is not updated.

Action:

Correct the errors and resubmit all the updates for this execution.

PROGRAM LOGIC ERROR IN LIBRARIAN.

Reason:

The system returned invalid code from a read or write operation.

Action:

Send documentation, including the SYSABEND dump, to Computer Associates Technical Support.

REINIT PROHIBITED; NO/INACTIVE SECURITY SYSTEM OR FILE UNDEFINED AS SECURITY SYSTEM RESOURCE.

Reason:

AllFusion CA‑Librarian master file reinitialization was prohibited because a security-related reinitialization parameter was specified, but one of the following conditions exist:

• There is no security system,
• Your security system is inactive, or
• The master file was not defined to your security system.

Action:

Remove the security-related parameter or contact your security administrator.

RENAME FAILED FOR OSJOB DATASET. PROCESSING CONTINUES USING ORIGINAL NAME BUT DATA SET MAY BE DELETED BY INITIATOR AT STEP TERMINATION.

Reason:

The rename of the OSJOB data set failed. The system deletes the OSJOB data set if DISP on DD statement so specifies.

Action:

No action required.

module-name REPLACED ON THE JOBSTREAM FILE.

Action:

The specified module was replaced in the PDS that OSJOB defined. The EXEC(R) option was invoked.

Action:

No action required.

RESTORE FOUND INVALID DATA DURING ITS START MODULE PROCESS; MODULE(S) MISSING ON RESTORED MASTER.

Reason:

The backup tape contained invalid data. One or more modules were not restored.

Action:

Restore the modules from an earlier backup.

RUN ABORTED - NO OPERATIONS WERE PERFORMED.

Reason:

Usually this message follows other messages indicating specific error conditions.

Action:

Correct the errors and rerun the job.

SECURITY INTERFACE ERROR; RUN TERMINATED.

Reason:

An error occurred in the AllFusion CA‑Librarian security interface.

Action:

Contact your systems programmer.

SECURITY SYSTEM INACTIVE; RUN TERMINATED.

Reason:

The security system at your site is inactive.

Action:

Contact your systems programmer.

SECURITY USER VIOLATION THRESHOLD EXCEEDED; RUN TERMINATED.

Reason:

Enough security violations were encountered during an AllFusion CA‑Librarian run to exceed the security system's defined user error threshold.

Action:

Correct the security violations and rerun the job.

SEQUENCE NUMBER ERROR.

Reason:

Sequence numbers in previous -INS, -REP, or -DEL statements are not in ascending order. The module is not updated.

Action:

Correct the error and resubmit the module update. If the SEQCHK option is in effect, data statements must be in ascending order at -ADD time.

SEQUENCE NUMBER IN LAST CONTROL STATEMENT NOT FOUND.

Reason:

The sequence number specified in the last -INS, -REP, or -DEL statement was not found in the module. The module was not updated.

Action:

Verify that the correct sequence number was specified.

SIMULTANEOUS UPDATE OF SAME MODULE FROM ANOTHER PROCESSOR HAS BEEN DETECTED.

Reason:

Self-explanatory.

Action:

Rerun the job.

SKIPPING MODULE module-name WHICH IS OUT OF SEQUENCE ON THE BACKUP TAPE.

Reason:

During a master file restore, AllFusion CA‑Librarian determined a module is out of order and is skipping it to ensure that the modules on the resulting tape master file are in sequence.

Action:

Recover the module from an alternative backup tape using UTILITY -COPY.

SOURCE RECORDS AFTER -DEL STATEMENT.

Reason:

Source statements must not follow a -DEL command.

Action:

Remove the statements and resubmit the update.

SPECIFIED DATA SET COULD NOT BE OPENED.

Reason:

You did not specify a DD statement for the -AUX input file.

Action:

Specify a DD statement for the -AUX input file.

SPECIFIED MODULE LEVEL NOT FOUND, OR COMBINATION OF ARC= AND ARCLR OPTION IS INVALID.

Reason:

You specified an invalid level number in the ARC= option.

Action:

Examine the master file index listing to determine the number of levels that are maintained for the module. Correct the ARC= and ARCLR= options and resubmit the update.

This message is also issued when the ARC= and ARCLR= specifications conflict (for example, ARC=781203, ARCLR=781204).

STARTING SEQUENCE NUMBER NOT FOUND.

Reason:

There is an invalid sequence number on the -REP, -DEL, or -INC command. All updates for this module are bypassed.

Action:

Correct the error and resubmit the module update.

STATEMENT OTHER THAN A -SCAN OR -END FOLLOWS A -SCAN STATEMENT.

Reason:

There was an invalid statement in the global scan execution. The current execution is aborted.

Action:

Remove the offending statement and resubmit the job.

STORAGE UNAVAILABLE FOR WORK AREA. COBOL COPY DEACTIVATED FOR THIS RUN.

Reason:

AllFusion CA‑Librarian's request for storage failed.

Action:

Resubmit the job in a larger partition.

STRING RESULTING FROM PREFIX REPLACEMENT IS TOO LONG. PREFIX REPLACEMENT IS NOT SUPPRESSED. PREFIX IN ERROR: prefix.

Reason:

Prefix replacement during expansion of a COBOL COPY verb resulted in a character string that is too long for one statement.

Action:

The prefix that caused the error is printed out to simplify location of the statement in error.

SYNTAX ERRORS FOUND. 'EXEC' SUPPRESSED, 'LIST' INVOKED.

Reason:

Syntax errors were found and the suppress code was specified in the SYNCHK option. The module is listed and updated, but not written to the job stream file.

Action:

Correct the specified syntax errors and retry.

SYSIN DATA SET COULD NOT BE OPENED.

Reason:

You did not specify a SYSIN data set for an AllFusion CA‑Librarian execution. The execution is canceled.

Action:

Resubmit the job, providing a SYSIN data set.

SYSnnn UNASSIGNED/ASSIGNED TO UNSUPPORTED DEVICE. OUTPUT TO LISTING/INDEX FILE (IF ANY) SUPPRESSED.

Reason:

Unless reassigned during LIBGEN assembly, either the VSE/ESA work file used for module listings or the master file index (SYS001 or SYS002) is either unassigned or assigned to an unsupported device. Output the LIST or INDEX options produce do not appear in the AllFusion CA‑Librarian output. The named work file (SYSnnn) needed for this VSE/ESA execution of AllFusion CA‑Librarian is either unassigned or assigned to an unsupported device. The execution was canceled.

Action:

Correctly assign SYSnnn and resubmit the job.

SYSTEM INTEGRITY ERROR The LIBRARIAN SYSTEM RELEASE DATES OF THE REENTRANT AND NON-REENTRANT LOAD MODULES DO NOT AGREE. LOAD MODULE SYSTEM DATE VERSION # REENTRANT mm/dd/yy n.n NON-REENTRANT mm/dd/yy n.n

Reason:

An error was made while installing AllFusion CA‑Librarian. The reentrant and non-reentrant executable modules for the batch AllFusion CA‑Librarian are not the same version.

For z/OS and OS/390, the default name of the non-reentrant load module is AFOLIBR. The name of the reentrant load module is EPXVWVZP. A common cause of this message is that an older version of EPXVWVZP is loaded from the LPA, while a newer version of AFOLIBR is loaded from a private library. In this case, load the new version of EPXVWVZP into the LPA and rerun the job.

For VSE/ESA, the default name of the non-reentrant phase is LIBRPROG. The default name of the reentrant phase is LIBRMAIN. A common cause of this message is that an older version of LIBRMAIN is loaded from the SVA, while a newer version of LIBRPROG is loaded from a private library. In this case, load the new version of LIBRMAIN into the SVA and rerun the job.

Action:

Review and correct your installation procedure as the message indicates.

SYS006 (ALTERNATE M/F) IS NOT ASSIGNED TO A VALID LIBRARIAN MASTER FILE. COPY EXPANSION SUPPRESSED.

Reason:

SYS006 or the logical unit number substituted for SYS006 during LIBGEN assembly is not assigned to a valid AllFusion CA‑Librarian master file.

Action:

If an alternate master file is not used, unassign SYS006 and resubmit the job.

SYSUT1 DD STATEMENT MISSING.

Reason:

Condition code 16. The JCL used to invoke the z/OS and OS/390 Comparator did not include a DD statement named SYSUT1.

Action:

Supply a DD statement for SYSUT1 and resubmit the job.

SYSUT2 DD STATEMENT MISSING.

Reason:

Condition code 16. The JCL used to invoke the z/OS and OS/390 Comparator did not include a DD statement named SYSUT2.

Action:

Supply a DD statement for SYSUT2 and resubmit the job.

SYSUT3 DD STATEMENT MISSING.

Reason:

Condition code 16. The z/OS and OS/390 Comparator needed the work file the SYSUT3 DD statement normally defines, but the JCL used to invoke the Comparator included no such DD statement. No comparison is performed.

Action:

Supply a DD statement for SYSUT3 and resubmit the job.

SYSUT3 DD STATEMENT UNACCEPTABLE.

Reason:

Condition code 16. The z/OS and OS/390 Comparator needed the work file the SYSUT3 DD statement normally defines, but the DD statement defined either a concatenation of data sets, a multivolume data set, or a data set not on either a tape or direct access device. No comparison is performed.

Action:

Supply a valid DD statement for SYSUT3 and resubmit the job.

SYSUT4 DD STATEMENT MISSING.

Reason:

Condition code 16. The z/OS and OS/390 Comparator needed the work file the SYSUT4 DD statement normally defines, but the JCL used to invoke the Comparator included no such DD statement. No comparison is performed.

Action:

Supply a valid DD statement for SYSUT4 and resubmit the job.

SYSUT4 DD STATEMENT UNACCEPTABLE.

Reason:

Condition code 16. The z/OS and OS/390 Comparator needed the work file the SYSUT4 DD statement normally defines, but the DD statement defined either a concatenation of data sets, a multivolume data set, or a data set not on either a tape or direct-access volume. No comparison is performed.

Action:

Supply a valid DD statement for SYSUT4 and resubmit the job.

TAPE BLOCK SIZE tape-block size REQUESTED BLOCK SIZE requested- block size EXCESS UNUSED.

Reason:

The actual block size of the restore tape, tape-block size, is smaller than the block size specified in the BLKSIZE parameter on the -OPT RESTORE command, requested-block size.

The excess memory is unused.

Action:

No action required.

TAPE BLOCK SIZE tape-block size REQUESTED BLOCK SIZE requested- block size RUN TERMINATED.

Reason:

The actual block size of the restore tape, tape-block size, is larger than the block size specified in the BLKSIZE parameter on the -OPT RESTORE command, requested-block size.

Action:

Re-run the job with the correct block size specified.

THE FILE DEFINED BY THE SYSUT1 DD STATEMENT CONTAINS NO RECORDS.

Reason:

Condition code 4. The file the SYSUT1 DD statement defined contains no records. z/OS and OS/390 Comparator does not write a File Comparison report.

Action:

Verify that the correct file is specified for SYSUT1.

THE FILE DEFINED BY THE SYSUT2 DD STATEMENT CONTAINS NO RECORDS.

Reason:

Condition code 4. The file the SYSUT2 DD statement defined contains no records. z/OS and OS/390 Comparator does not write a File Comparison report.

Action:

Verify that the correct file is specified for SYSUT2.

THE INPUT FILES ARE EQUAL.

Reason:

Condition code 0. During an execution of the z/OS and OS/390 Comparator, either the files the SYSUT1 and SYSUT2 DD statements defined are identical and you specified SEQFLD=NONE or the input files are both empty. No File Comparison report is written.

Action:

No action required.

THIS LISTING TERMINATED DUE TO TABLE OVERFLOW. SEE UPDATE RECORD LISTING FOR RESULTS OF THE REMAINING OPERATION.

Reason:

The Summary of Activity lists only 400 modules, however, processing continues.

Action:

Check the Update Record listing for the status of remaining modules.

THIS RUN SHOULD HAVE CREATED A BACKUP FILE, BUT THE FILE WAS NOT DEFINED BY JCL. IF A BACKUP FILE IS NEEDED, IT WILL BE NECESSARY TO REQUEST ITS CREATION AS SOON AS POSSIBLE.

Reason:

The backup file was not assigned. The current execution was completed, however, and no backup tape was taken.

Action:

Assign the backup file, remove all updates, put the operand BKUPTAPE in the -OPT statement, and resubmit the job.

TOO MANY STATEMENTS AFTER -SEL.

Reason:

More than 30 statement follow the GPO -SEL command.

Action:

Remove some of the statements after the -SEL command and resubmit the job.

TOO MANY EDIT/SCAN COMMANDS.

Reason:

You specified too many -EDIT, -SCAN, or -FILL commands.

Action:

See the Batch Command Reference Guide for the maximum number of -EDIT, -SCAN, or -FILL statements.

UNACCEPTABLE MODULE CONTROL STATEMENT; ONLY UTILITY -COPY GENERATED -ADD NOW ACCEPTED.

Reason:

Direct tape master updating is not supported.

Action:

You can only use the batch UTILITY -COPY control statement to add modules to a tape master.

UNAUTHORIZED ACCESS.

Reason:

Self-explanatory.

Action:

Contact your supervisor.

UNAUTHORIZED ACCESS, MODULE LEVELS CANNOT BE CLEARED.

Reason:

Self-explanatory.

Action:

Contact your supervisor.

UNAUTHORIZED ATTEMPT TO ACCESS RESTRICTED MODULE.

Reason:

Self-explanatory.

Action:

Contact your supervisor.

UNBALANCED PARENTHESIS

Reason:

The GPO control statement contains an incomplete pair of parentheses.

Action:

Add or delete a parenthesis and resubmit.

UNIT cuu HAS BECOME INOPERABLE.

Reason:

The unit containing the master file was not operational after the master file was defined.

Action:

See the operator, who must define the master file again before it can be used.

UNIT cuu HAS BEEN UNLOADED DURING USE.

Reason:

The unit containing the master file was unloaded after the master file was defined.

Action:

See the operator, who must define the master file again before it can be used.

UNIT cuu NOT OPERATIONAL.

Reason:

The specified unit was not operational.

Action:

Contact the operator.

module-name UNSUCCESSFULLY STOWED.

Reason:

One of the following occurred:

• The module was unsuccessfully stowed in the OSJOB data set because a module with the same name already exists in that PDS.
• There was insufficient space in the PDS.
• There were not enough directory blocks.

Action:

Use the EXEC(R) operand to replace the module.

module-name UNSUCCESSFULLY STOWED. NO STATEMENTS FOR JOBSTREAM FILE.

Reason:

The selected module contained no statements and, therefore, was not written to the OSJOB data set.

Action:

No action required.

UPDATES NOT IN ORDER BY SEQUENCE NUMBER.

Reason:

The -INS, -REP, and -DEL statements must specify sequence numbers in ascending order.

Action:

Correct the error and resubmit the update.

USER RETURN CODE 16 INTERCEPTED -- UPDATE TERMINATED.

Reason:

A violation of installation standards occurred. Processing for the current module is terminated.

Action:

Contact your supervisor.

USER RETURN CODE 20 INTERCEPTED -- RUN TERMINATED.

Reason:

A violation of installation standards occurred. Processing for the current module is terminated.

Action:

Contact your supervisor.

VOLUME MOUNTED ON UNIT cuu IS NOT DOS OR OS VOLUME.

Reason:

The volume mounted on the specified unit does not have a standard z/OS and OS/390 or VSE/ESA label.

Action:

Contact your systems programmer or specify another volume.

VSAM BACKUP FILE TO BE INITIALIZED IMPROPERLY DEFINED.

Reason:

AllFusion CA‑Librarian was attempting to initialize a backup file during a disk-to-disk backup. The assigned file appears in the VSAM catalog, but is not defined as a VSAM cluster that has an associated data catalog entry.

Action:

Check your DLBL job control statements for the filename BACKUP or redefine the file correctly.

VSAM FILE TO BE INITIALIZED IMPROPERLY DEFINED.

Reason:

AllFusion CA‑Librarian was attempting to initialize a VSAM master file. The assigned file appears in the VSAM catalog, but is not defined as a VSAM cluster that has an associated data catalog entry.

Action:

Check your DLBL job control statements for the filename MASTER or redefine the file correctly.

VSAM FILE TO BE OPENED IMPROPERLY DEFINED.

Reason:

AllFusion CA‑Librarian was attempting to process a VSAM master file. The assigned file appears in the VSAM catalog, but is not defined as a VSAM cluster that has an associated data catalog entry.

Action:

Check your DLBL job control statements for the filename MASTER or redefine the file correctly.

WARNING: -MCD STATEMENT IGNORED; ACCESS AUTHORITY INSUFFICIENT OR CANNOT BE DETERMINED.

Reason:

The AllFusion CA‑Librarian master file you tried to access is defined to a security system.

The -MCD statement you supplied to change the management code is ignored because you do not

have the proper authority.

Action:

Contact your security administrator.

WARNING: -MCD STATEMENT IGNORED; SECURITY ACCESS AUTHORITY TAKES PRIORITY.

Reason:

The AllFusion CA‑Librarian master file you tried to access is defined to a security system.

Since the defined access authorities take precedence, the -MCD statement is ignored.

Action:

No action required.

WORKFILE COULD NOT BE OPENED.

Reason:

The AllFusion CA‑Librarian work file is either incorrectly assigned or not assigned at all. The AllFusion CA‑Librarian execution is canceled.

Action:

Correct the error and resubmit the job.

For z/OS and OS/390: There is a missing or invalid DD statement, either SYSAF01, SYSAF02, or SYSAF03.