IAM SYSPRINT Messages
The following general messages are issued by various IAM utility programs. These messages are typically written to SYSPRINT by the originating utility program. These are messages from the IAMRECVR, IAMSIMVS, IAMSMFVS, IAMSMF, and IAMZAPOP utility programs provided with the IAM product.
Number | Description |
|---|---|
IAM099 | NEAR RELATIVE DATA LOCATION nnnn 'error description' Explanation: The common parsing routine encountered an error in parsing the user-specified control statements. The approximate location of the error was position nnnn, counting the first position as 000. System Action: Correct the error and resubmit job. |
IAM100 | IAM FILE ANALYSIS - DSN= dataset name Explanation: This report is produced from a LISTCAT request on the IAMPRINT DD output, and also on SYSPRINT when IAMRECVR is run against an IAM file. The report contains descriptive information and statistics about the IAM file. For a complete description of the output report following this message, please refer to the LISTCAT Report description in IAMPRINT Report in the IAM Space. System Action: None. This is an informational message only. |
IAM213 | 'file type' RECOVERY FILE CREATED DDNAME='ddname' Explanation: IAMRECVR has completed the output of a file to the DDNAME 'ddname'. The 'file type' is as follows: System Action: Refer to the documentation of IAMRECVR for the uses of the different output files it creates. |
IAM260 | LISTC PROCESSING FAILED FOR DSN='dsname' Explanation: An error occurred during IAM processing of an IDCAMS LISTC command for a possible IAM file. This message will be preceded by one or more error messages describing the error in more detail. System Action: Review other messages for source of error, and correct as necessary. IDCAMS LISTC processing will continue normally, however, no information will appear in the IAMPRINT file for the named file. |
IAM262 | DATASET IS NOT AN IAM FILE Explanation: During an IDCAMS LISTC IAM attempted to process a data set as an IAM file, however, it was determined that the data set was not an IAM file. The data set name is displayed in the IAM260 message. System Action: None. This is an informational message only. |
IAM266 | LOAD OF MODULE 'modulename' FAILED Explanation: During an IDCAMS LISTC command, IAM encountered an error loading the named support module. There should also be an accompanying message in SYSLOG indicating the cause of the problem (i.e. S106, S306, or S806 error). The data set name is presented in the accompanying IAM260 message. System Action: Find the IBM error message, and take corrective action. Possibilities are insufficient virtual storage to load the module, or IAM is not in the system LINKLIST and no STEPLIB has been provided. |
IAM269 | IAM CPL PROCESSING FAILED Explanation: IAM was attempting to process a CATALOG parameter list to determine data set name and volume information, however, the CPL did not contain the expected information. There will be no information listed about the IAM file. System Action: Contact BMC support for assistance. |
IAM303 | CARD IMAGE -- * control statement image * Explanation: A display of the SYSIN data set input control statements. System Action: None. Information message only. |
IAM316 | RECOVERY CAN BE FORCED BY SPECIFYING VALUES FOR THE FOLLOWING - Explanation: An attempt was made to recover an IAM file that has damaged control records. The unreadable control records requires the user to specify key data normally extracted from the file. System Action: The next lines displayed will detail the fields required. Use this information to continue the recovery. |
IAM318 | *WARNING* DATASET-'dsn' DEFINED FIXED CONTAINS VARIABLE LEN RECORDS Explanation: The DEFINE for this cluster shows the average and maximum record lengths to be equal. IAMSIMVS detected one or more records that were not equal to the average record length Defined for this cluster. System Action: IAMSIMVS continues processing as if the file contained fixed length records. Blocking, overflow and other values established for a file, however, vary depending upon whether record lengths are fixed or variable. To obtain a more accurate estimate of IAM's space savings for this file, include the 'VARIABLE' keyword with the 'SELECT' option. |
IAM319 | PREMATURE END OF FILE -- AFTER BLOCK nnnnnnnn Explanation: IAMRECVR detected a premature end of file at block nnnnnnn. Data blocks may have been lost. System Action: Review the contents of the recovered file. A section of the file being recovered may not have been readable. |
IAM320 | MAXIMUM BLOCKS LOST DUE TO END OF FILE -- nnnnnnnn Explanation: An end of file error erases the remainder of the track. The reported number of blocks could have existed on the track but were not yet read when the end of file was encountered. System Action: Review the contents of the recovered file. A section of the file being recovered may not have been readable. |
IAM321 | INVALID VARIABLE LENGTH FIELD -- BLOCK nnnnnnnn Explanation: IAMRECVR detected an invalid RDW length field for a given record (that is, RDW exceeds maximum LRECL). The block number is printed and the remainder of block is bypassed. System Action: Review the contents of the recovered file. A section of the file being recovered may not have been readable. |
IAM322 | DROPPED DUE TO I/O ERROR -- BLOCK nnnnnnnn Explanation: IAMRECVR has dropped block nnnnnnnn. The first 24 bytes of the block at the location of the errors is printed in hexadecimal. Processing continues. System Action: Review the contents of the recovered file. A section of the file being recovered may not have been readable. |
IAM323 | SEQUENCE CHECK -- BLOCK nnnnnnnn Explanation: An out of sequence record was encountered. The IAM block number is printed along with 24 bytes of the key in hexadecimal. Processing continues. System Action: Review the contents of the recovered file. A section of the file being recovered may not have been readable. |
IAM324 | UNABLE TO CALCULATE LOST BLOCKS - ASSUMING nn MISSING Explanation: An end of file erases the remainder of the track. Any blocks that were on the track at the time the EOF record was created have been destroyed. System Action: Review the contents of the recovered file. A section of the file being recovered may not have been readable. |
IAM325 | FILE NOT COMPRESSABLE - DATA LEN PAST KEY < 11 BYTES - DSN= Explanation: IAMSIMVS determined that the records contained within the file were not eligible for IAM record compression. IAM only compresses the data in a record located past the end of the key and only if the length of that data is more than 10 bytes. (that is, MAXLRECL-(RKP+KEYLEN) > 10). System Action: No action is required. IAMSIMVS will continue the simulation for the file as if it were not converted to an IAM file in compressed format. |
IAM325 | ERROR DECOMPRESSING RECORD – BLOCK nnnn Explanation: IAMRECVR was unable to decompress a compressed record from an IAM data set. System Action: Most probable cause is that a corrupted buffer was written out to the data set. If possible, recover the file through other means. If that is not possible then continue IAMRECVR will recover all the records that it is able to read, but will drop the rest of the records. Backup the data set as described in the User’s Guide section of the IAM Space, and contact BMC for support. |
IAM326 | IAMCRTSM ERROR -- 'error description' -- DSN=dsn Explanation: IAMCRTSM was invoked to simulate the conversion of a VSAM file and encountered a logical error. The error description will be in the format: INVALID BLOCKSIZE/BLOCKING FACTOR CODE=nnn. The CODE=nnn translates directly into an IAM create abend code (see IAM user abend, error, and completion codes later in this section). System Action: If the message was issued for invalid blocking, ensure that the block size specified is both larger than the record length and compatible with the device. If the CODE= message is issued, refer to the actions for the associated IAM create abend code. |
IAM340 | 'recovery operation' - DSN= 'dsname' Explanation: Describes the user specified IAM file 'recovery operation' and the name of the IAM file being processed. System Action: None. This is an informational message only. |
IAM341 | CONTROL BREAKS IN OVERFLOW BLOCKS -- = nnnn nnnn Explanation: Issued by the DIAGNOSE and RECOVER operations of the IAM file recovery program IAMRECVR, indicating that records within the overflow blocks of the file being processed are out of sequence. System Action: When issued during RECOVER, it indicates that the RECOVER output is out of sequence and must be sorted, either by IAMRECVR or externally prior to an IAM create. When issued during DIAGNOSE, no additional processing is necessary. |
IAM342 | IAM FILE CONTAINS NO DETECTABLE ERRORS Explanation: Issued by the DIAGNOSE and RECOVER operations of the IAM file recovery program IAMRECVR, indicating that the IAM file is not damaged and is acceptable for IAM processing. System Action: None. This is an informational message only. |
IAM343 | SEQUENCE ERRORS IN DATA BLOCKS -- = nnnnnnnnExplanation: Issued by the DIAGNOSE and RECOVER operations of the IAM file recovery program IAMRECVR, indicating physical damage to the IAM file. System Action: The file must be created again from a suitable backup or recovered and reconstructed. Prior to create, sort the data set output from the RECOVER operation. |
IAM344 | NUMBER OF DROPPED BLOCKS -- = nnnnnnnnExplanation: Issued by the DIAGNOSE and RECOVER operations of the IAM file recovery program IAMRECVR, indicating physical damage to the IAM file. IAMRECVR encountered I/O errors during the processing of the IAM file and nnnnnnnn blocks were dropped from the file. System Action: The file must be created again from a suitable backup or recovered and reconstructed. Prior to create, sort the data set output from the RECOVER operation. |
IAM345 | NUMBER OF DUPLICATE RECORDS -- = nnnnnnnn Explanation: Issued by the DIAGNOSE and RECOVER operations of the IAM file recovery program IAMRECVR, indicating that duplicate keys were found in the IAM file. During a RECOVER operation, duplicate records can be ignored, printed, logged for subsequent application to the file, or applied directly if an IAM file is being created as the output of the recovery program. System Action: See the documentation for the RECOVER program, DUPLICATES operand. The file must be created again from a suitable backup or recovered and reconstructed. Prior to create, sort the data set output from the RECOVER operation. |
IAM346 | SPANNED RECORDS EXTRACTED --- = nnnnnnnn Explanation: Issued by the IAMRECVR RECOVER command when spanned records have been recovered and placed in the data set identified by the SPANOUT DD statement. System Action: To recover the spanned records, run the IAMRECVR APPLY SPANNED command, which will read the SPANOUT data set, and insert the records back into the IAM data set. |
IAM360 | STEP - ssssssss DDNAME - 'ddname' DATASET MONITORED - 'dsname' Explanation: Identifies the IAM job step name, the DDNAME and, optionally, the data set name of the IAM file being processed by the information service routines of the IAM monitor facility. System Action: None. This is an informational message only. |
IAM361 | INFO REQUESTED BY PROGRAM 'program' PERFORMING 'description' PROCESSING Explanation: Identifies the IAM processing program that requested the printing of the information block, the type of processing being performed, and the time the information block was printed by the information service routines of the IAM INFO report. System Action: None. This is an informational message only. |
IAM362 | DATA CHARACTERISTICS Explanation: Heading line which always precedes the IAM data characteristics when listed by the IAMINFO report. System Action: None. This is an informational message only. For further detail on these fields see IAMINFO-Reports: IAM362. |
IAM363 | IAM FILE CHARACTERISTICS Explanation: Heading line which always precedes the IAM file characteristics when listed by the IAMINFO report. System Action: None. This is an informational message only. For further detail on these fields see IAMINFO-Reports: IAM363. |
IAM364 | IAM OVERFLOW CHARACTERISTICS Explanation: Heading line which always precedes the IAM overflow characteristics when listed by the IAMINFO report. System Action: None. This is an informational message for IAM Compatible format files only. |
IAM365 | IAM EXECUTION STATISTICS Explanation: Heading line which always precedes the IAM execution statistics when listed by the IAMINFO report. System Action: None. This is an informational message only. For further detail on these fields see IAMINFO-Reports: 365. |
IAM366 | IAM COMMAND EXECUTED SUMMARY Explanation: Heading line which always precedes the IAM command summary when listed by the IAMINFO report. System Action: None. This is an informational message only. For further detail on these fields see IAMINFO-Reports: IAM366. |
IAM367 | THERE WAS INSUFFICIENT STORAGE AVAILABLE TO ACQUIRE ADDITIONAL BUFFERS Explanation: IAM's Real Time Tuning tried to acquire additional data buffers but there was insufficient virtual storage available. System Action: Increase the REGION value on the JOB statement or the EXEC statement so the next execution of the job will have storage available to acquire additional buffers. |
IAM368 | SPECIFYING A BUFNO VALUE GREATER THAN nn MAY IMPROVE PERFORMANCE Explanation: IAM's Real Time Tuning buffer management found that, for this mix of data and file processing commands, if additional buffers had been available they would have been acquired. Additional buffers were not acquired because it would have exceeded the maximum buffers allowed for this job. System Action: If you wish to increase the maximum buffers for this job, specify the MAXBUFNO=nn parameter on the IAM Override Control statement for this IAM file. |
IAM369 | IAM OVERRIDES - Explanation: The IAMINFO report displays the IAM Override Options that were used for the processing of the file that this IAMINFO report is reporting on. System Action: None. This is an informational message only. |
IAM371 | INCREASING THE NUMBER OF PRIME EXTENSION BLOCKS MAY IMPROVE PERFORMANCE Explanation: An attempt to insert a record into prime extension failed because the prime extension was full. The record was inserted into independent overflow instead. System Action: Define the IAM file with a larger prime extension. |
IAM372 | IAM EXTENDED AREA CHARACTERISTICS Explanation: This heading line always precedes the description of the IAM Extended Area (Enhanced format files only). See IAMINFO-Reports: IAM372. |
IAM373 | REORGANIZATION OF THIS FILE IS RECOMMENDED Explanation: During Open and/or Close processing, IAM noticed that the size of the extended overflow area was such that it could cause a performance degradation. As a preventative measure, it is recommended, but not required, that the file be reorganized to move records out of the overflow area. This IAMINFO message should be accompanied with an IAMW22 message, which will indicate the reason that a reorganization is being recommended. System Action: No action is required, but a file reorganization is recommended to be scheduled in the near future. |
IAM374 | WAITED FOR ENCRYPTION BUFFERS Explanation: This message is part of the IAMINFO report if during the Open-Close file period for an IAM encrypted file there was a wait for write encryption buffers to become available. System Action: If file I/O performance were being analyzed then bring this message to the attention of IAM technical support. Otherwise the message is informational. |
IAM400 | 'processing function' - 'progname' - VER v.r. - COMPUWARE CORP - DATE: 'yyddd' PAGE: 'nn' Explanation: Generalized page header for the named 'processing functions' which are provided by the 'program' named in the printed title. System Action: None. This is an informational message only. |
IAM401 | PARM DATA - * parm-field-data * Explanation: Displays the program control information specified in the “PARM=” field of the EXEC statement. This data will not be displayed if program is invoked under TSO. System Action: None. This is an informational message only. |
IAM402 | INVALID CONTINUATION Explanation: User coded a delimiting comma following the last keyword on a control statement and did not provide the next logical record. System Action: Correct and resubmit job. |
IAM403 | REQUIRED OPERANDs NOT SPECIFIED - cc...cc Explanation: The operand cc...cc is required for the execution of the command. It must be specified; no defaults are available. System Action: Correct and resubmit job. |
IAM404 | WORKING STORAGE AREA SIZE OF nn BYTES EXCEEDED - SUBCOMMAND IGNOREDExplanation: The maximum number of working storage bytes available to the subcommands has been exceeded. System Action: The number of bytes available for subcommand working storage is derived from the 'MAXCORE' operand, which has a lower limit of 1000 bytes and an upper limit of 120000 bytes. If the upper limit has been reached, call BMC support. If the upper limit has not been reached, resubmit the job specifying a value for 'MAXCORE' greater than the number displayed. |
IAM405 | MAXIMUM CONTINUATION COUNT OF nnnn EXCEEDED - COMMAND FLUSHED Explanation: The user control statement used too many continuations. System Action: Reduce the number of continuations to the value nnnn. Resubmit the job. |
IAM407 | CONTROL STATEMENT ERROR - 'action taken' Explanation: An error was encountered during the processing of user supplied control statements. Always preceded by one or more messages which define and delimit the errors. The 'action taken' is one of the following: System Action: Correct and resubmit job. |
IAM408 | NO CONTROL STATEMENTS WERE FOUND JOB TERMINATED Explanation: SYSIN data set is empty or contained only comment statements ('*' in column 1). |
IAM410 | DSNAME='dsname' -- 'error description' -- PROCESSING BYPASSED Explanation: The 'data set name' printed encountered the 'error' described and subsequent processing was bypassed. The error description can be one of the following: System Action: Check the data set name for correctness. If the wrong data set name was specified, specify the correct data set name and resubmit the job. If the message indicates the data set is not an IAM file it is because the IAM control record was not present. Use program IAMRECVR specifying the IAM file characteristics on the 'RECOVER' subcommand to facilitate data recovery. |
IAM413 | DSN/DSG INDEX ERROR - 'error description' Explanation: When using the index level option to select data sets or data set groups the user either: System Action: Correct and resubmit. |
IAM418 | COMMAND PROCESSING DETECTED ERROR -- 'action taken' Explanation: An error was encountered during the processing of the subcommand specified on a user supplied control statement. Always preceded by one or more messages that define and delimit the errors. The action taken is one of the following: System Action: Correct and resubmit job. |
IAM421 | LOCATE ERROR -- 'error description' - DSN='dsname' Explanation: A LOCATE SVC was issued requesting identification of the component named by DSN='dsname'. The LOCATE either failed or returned a component: cluster name type code that is not currently supported. Action: Do one of the following: For the RETURN CODE type of error, look up the codes under message IDC3009I. The most likely cause is a STEPCAT or JOBCAT DD statement was not supplied for a user catalog that has entries in it for components on the volumes being processed, and those entries are not ALIAS'ed. |
IAM465 | UNABLE TO OPEN (DDNAME=DSN=)'name' - 'reason' Explanation: The 'ddname' named in the message failed to OPEN for the 'reason' shown in the text. The recognized reasons are: System Action: If the named 'ddname' is required for the requested operation correct the error and resubmit the job, otherwise the message may be ignored. |
IAM471 | DDNAME='ddname' I/O ERROR -- SYNAD='message' Explanation: A permanent I/O error was detected on the data set referenced by the DDNAME 'ddname'. System Action: Examine the SYNADAF message to determine the cause of the error. The format of this message is documented in IBM SRL publications. Call BMC support for additional assistance. |
IAM476 | DDNAME='ddname' REFERENCES A DEVICE TYPE OTHER THAN DISK Explanation: The DDNAME 'ddname' listed can only be allocated to a disk device. System Action: Check the unit specification in the JCL for errors, correct and resubmit. |
IAM484 | INTERNAL LOGIC ERROR -- JOB TERMINATED Explanation: The program has encountered an illogical condition. System Action: Call BMC support for additional assistance AFTER obtaining a storage dump. |
IAM485 | SORT FAILURE HAS OCCURRED RC='nn' - 'action description' Explanation: Your installation's sort product has set a return code other than zero. The return code problem description can be found in the sort Space supplied with the sort program product. In many cases the sort program will provide an error message on DDNAME SYSOUT and or on the system console. System Action: If you cannot correct the problem from this information, call BMC support for additional assistance. |
IAM491 | 'function' FUNCTION STARTED TIME=hh.mm.ss Explanation: Identifies type of function and time the function started. System Action: None. This is an informational message only. |
IAM492 | 'function' FUNCTION ENDED -- hh.mm.ss CONDITION CODE - nnnn Explanation: Identifies type of function and time the function ended. The return code is printed if it is non-zero. System Action: Review the completion code. If the completion code is greater than zero, check the output for the preceding messages that describe the reason for a non-zero completion. |
IAM493 | 'function' - BYPASSED -- PRIOR FUNCTION TERMINATED WITH KEYWORD OR COMMAND DETECTED ERROR Explanation: A previous command upon which this function may be dependent encountered serious errors. |
IAM495 | NO RECORDS MATCHED SELECTION CRITERIA Explanation: The selection criteria specified did not cause any records to be selected for processing. If program IAMSMFVS, this message will also appear if the required SMF record types are not being collected. System Action: Make sure the selection criteria is correct. |
IAM496 | MODULE 'modname' -- NOT USABLE WITH RELEASE v.r. PROGRAMS -- EXECUTION TERMINATED Explanation: Module 'modname' is a release/version that is incompatible with the load module being executed. System Action: Check for a STEPLIB/JOBLIB DD statement pointing to a library other than the correct library for the product level you expect to use. If present, correct the library name and resubmit the job. If there is no STEPLIB/JOBLIB present, the module 'modname' is being obtained from a LINKLIST library. Add a STEPLIB or JOBLIB DD statement specifying the correct load module library and resubmit the job. |
IAM497 | cc..cc ABNORMALLY TERMINATED DUE TO KEYWORD/COMMAND DETECTED ERRORS Explanation: The common parsing routine encountered errors in parsing the user specified control statements. In addition, the user has set the option KWDCC=ABEND via program IAMZAPOP. Always preceded by one or more error description messages. System Action: Previous messages describe the errors; see those messages for further details. |
IAM498 | cc...cc PROCESSING COMPLETED WITH ERRORS Explanation: The named program completed the requested processing but encountered abnormalities in the process. System Action: Check the output for preceding messages that may describe the errors in detail. |
IAM499 | cc...cc PROCESSING COMPLETED Explanation: The named program has completed processing as requested. System Action: Check the output for messages that describe the results. |
IAM516 | CAMLST REGISTERS R0=nnnnnnnn R1=nnnnnnnn R15=nnnnnnnn Explanation: A CAMLST request failed. The type of CAMLST function (shown in the immediately preceding message) and the registers make diagnosing the problem relatively simple. The return codes from catalog management is(are) documented in the IBM SRL SYSTEM PROGRAMMING LIBRARY: DATA MANAGEMENT (for MVS) or CATALOG ADMINISTRATION GUIDE (for MVS/XA) or DATA MANAGEMENT FOR SYSTEM PROGRAMMERS (for non-MVS). System Action: Check the return codes and take corrective action if the error is apparent or call BMC support for additional assistance. |
IAM530 | MODULE 'modname' NOT FOUND - 'ddname' - 'dsname' Explanation: A BLDL was issued for the module 'modname' in the data set 'dsname' referenced by 'ddname' and the module was not found. The module is required to support a requested processing function. System Action: Verify that the library data set name 'dsname' specified on the 'ddname' statement was correct. If incorrect, correct it and resubmit the job. If the data set name is correct, check the IAM product install listing to see that all steps executed successfully. If required, rerun the installation steps missed. If necessary, contact BMC support for additional assistance. |
IAM531 | MODULE 'modname' CONTAINS NO TEXT RECORDS - 'ddname' - 'dsname' Explanation: When an attempt was made to read the module 'modname' in the data set 'dsname' referenced by 'ddname' and no text records were found. The module is required to support a requested processing function. System Action: Verify that the library data set name 'dsname' specified on the 'ddname' statement was the correct one. If incorrect, change and resubmit the job. If the data set name is correct, check the IAM product install listing to see that all steps executed successfully. If required, rerun the installation steps missed. If necessary, contact BMC support for additional assistance. |
IAM532 | MODULE 'modname' I/O ERROR READING - 'ddname' - 'dsname' Explianation: When an attempt was made to read the module 'modname' in the data set 'dsname' referenced by 'ddname' an I/O error was encountered. The module is required to support a requested processing function. System Action: Check the SYNAD error messages and MINI DUMP produced to see if the cause of the error is an obvious one. If so, correct and resubmit the job. If necessary, contact BMC support for additional assistance. |
IAM533 | MODULE 'modname' I/O ERROR WRITING - 'ddname' - 'dsname' Explanation: When an attempt was made to write the module 'modname' in the data set 'dsname' referenced by 'ddname' an I/O error was encountered. System Action: This is a serious error which may result in the load module library referenced by 'dsname' being unusable. If necessary, restore or recreate the library. Check the SYNAD error messages and MINI DUMP produced to see if the cause of the error is an obvious one. If so, correct and resubmit the job. If necessary, contact BMC support for additional assistance. |
IAM534 | 'ddname' OPEN FAILURE -- AVAILABLE COMMANDS: HELP, END Explanation: The required 'ddname' statement could not be OPENed. Commands which access modules in the 'ddname' data set cannot be executed. System Action: If the 'ddname' data set is required for the operation being attempted, correct and resubmit the job. Otherwise, none, information only. |
IAM535 | MODULE 'modname' READ UNSUCCESSFUL -- 'command' BYPASSED Explanation: The user requested function 'command' be performed against module 'modname' but the module was not successfully read. This message will be preceded by message IAM530, IAM531, or IAM532 detailing the reason the read failed. System Action: See message IAM530, IAM531, or IAM532, as required. |
IAM538 | MODULE 'modname' -- WRONG VER/LEVEL 'ddname' - 'dsname' Explanation: Module 'modname' is a release/version that is incompatible with the load module being executed. System Action: Verify that the 'ddname' DD statement is pointing to the correct library for the product level you expect to use. If incorrect, change and resubmit the job. If the data set name is correct, check the IAM product install listing to see that all steps were executed successfully. If required, rerun the installation steps missed. If necessary, contact BMC support for additional assistance. |
IAM539 | MODULE 'modname' 'function' - 'ddname'- 'dsname' Explanation: The module 'modname' from the data set dsname' referenced by 'ddname' has had function 'function' performed as requested by the user. System Action: None, information only. |
IAM540 | cccccccc CONTAINS INVALID CHARACTERS -- ZAP REJECTED Explanation: The value specified for the operand 'cccccccc' contained one or more characters that were not A-Z, 0-9, $#@. System Action: Remove the invalid characters and resubmit the job. |
IAM541 | THE FOLLOWING OPTIONS HAVE BEEN CHANGED IN -- 'dsname'Explanation: The AUDIT function has found changed options in the options table. The changed options will be listed. System Action: None. |
IAM542 | cccccccc CONTAINS INVALID INDEX STRUCTURE -- ZAP REJECTED Explanation: The value specified for the operand cccccccc contains two (2) or more consecutive periods (..) in violation of operating system data set naming conventions. System Action: Correct the errors and resubmit the job. |
IAM543 | cccccccc DOES NOT CONTAIN CHARACTER STRING cccccccc -- ZAP REJECTED Explanation: The value specified for the operand cccccccc does not contain the character string cccccccc as the required start of an index level. System Action: Correct the errors and resubmit the job. |
IAM544 | cccccccc REJECTED -- EXCEEDS MODIFIABLE PORTION OF IAMOPT Explanation: The length of the value specified for the operand cccccccc taken in conjunction with the offset operand exceeds the modifiable portion of the IAMOPT table. System Action: Correct the errors and resubmit the job. |
IAM545 | VERIFY FAILED -- CHAR/HEX PRINT FORCED Explanation: The VERIFY of existing contents failed. A character/hexadecimal print of the module IAMOPT is produced. Always preceded by message IAM544. System Action: See message IAM544. |
IAM546 | AUDIT REQUEST COMPLETE ALL DEFAULTS SET IN -- 'dsname' Explanation: The AUDIT function has found no changed options in the options table. System Action: None. |
IAM547 | AUDIT REQUEST COMPLETE FOR -- 'dsname' Explanation: The AUDIT function has completed. Changes were found and listed. System Action: None. |
IAM550 | ERRORS ENCOUNTERED DURING EXECUTION -- REWRITE CANCELED Explanation: One or more modules from the SYSLIB data set were scheduled for rewrite at termination or by the execution of a REWRITE command. However, previous commands failed to complete successfully. The errors encountered have been documented by preceding error messages. System Action: Correct the error conditions documented by the preceding error messages and resubmit the job. |
IAM561 | NON-NUMERIC DATA VALUE SPECIFIED FOR THE [FROMDATE | TODATE] KEYWORD Explanation: An invalid character string was specified for the indicated keyword. System Action: Correct the error condition. For information on valid values, refer to the IAMSMFVS-Reports of the space. |
IAM562 | INVALID VALUE SPECIFIED FOR [FROMDATE | TODATE] Explanation: An invalid numeric string was specified for the indicated keyword. System Action: Correct the error condition. For information on valid values, refer to the IAMSMFVS-Reports of the space. |
IAM569 | WARNING - cccccccc NOT CATALOGED - DSN='dsname' Explanation: The data set 'dsname' indicated is the new default for the file type indicated by cccccccc. A CAMLST LOCATE was issued to verify that the data set is cataloged as required for IAM to dynamically allocate. The data set name was not found by LOCATE. Message IAM516 detailing the CAMLST return codes is always printed following this message. System Action: See message IAM516. This is only a warning message. The data set name listed has become the new name of the indicated default. |
IAM574 | 'request' - DDNAME='ddname' - 'action' Explanation: Failed I/O 'request' resulting in the named 'action': System Action: Correct the reason for the error and resubmit the job. |
IAM600 | MAXSTACK VALUE OF nnnnnn EXCEEDED - SMF RCD PROCESSING TERMINATED Explanation: The SMF record processing subcommand being executed utilizes an in storage stack specified by the operand MAXSTACK. This storage stack is full. The specified size is insufficient to allow all of the selected SMF records to be processed. IAMSMF terminates without producing a report. System Action: Re-execute the program and specify the operand MAXSTACK= with a value greater than the value nnnnnn printed in this message. |
IAM601 | SMF RECORDS -- READ.nnnnnnnn USED.nnnnnnnn DROPPED.nnnnnnnn Explanation: Documents the SMF records processed as follows: System Action: None. This is an informational message only. |
IAM602 | FOLLOWING SMF RECORD DROPPED - LENGTH CHECK Explanation: User specified the CHECKLENGTH operand, causing all SMF records selected to be checked against a table of minimum lengths. This record failed the length check. The first 32 bytes of the record are printed in hexadecimal. System Action: Use the keyword RECSIZE=nn on the report control statement to specify an appropriate size. |
IAM603 | VSAM ERROR -- (DDNAME=DSN=)'name' 'error description' -- R15=xxxxxxxx -CODE=xxxxxxxx Explanation: An error occurred during the processing of a VSAM data set. The error description will be one of the following: System Action: Check the values of R15 and CODE against the return codes listed in the 'VSAM REFERENCE FOR MVS/370 DFP', 'VSAM ADMINISTRATION: MACRO INSTRUCTION REFERENCE FOR MVS/XA', or 'OS/VS VIRTUAL STORAGE ACCESS METHOD PROGRAMMER'S GUIDE', to determine the cause of the error. If possible, correct and re-execute the job. Call BMC support for additional assistance. |
IAM619 | MODULE 'modname' TOO LARGE TO PROCESS -- 'ddname' - 'dsname' Explanation: IAMZAPOP attempted to read the module 'modname' in the data set 'dsname' referenced by the statement 'ddname'. The module was required to support a processing functions but, due to the size of the module (or previously read modules), not enough buffer storage was available to complete the read. System Action: Run IAMZAPOP specifying 'ZAP BUFSIZE=nnnn', where nnnn is the size of the buffer in bytes. Specify a value between 122,880 and 3,145,728. After the buffer size has been changed, rerun the job that failed. |
IAM620 | MAXJOB VALUE OF nnnnn EXCEEDED - ADDITIONAL JOB NAMES BYPASSED Explanation: The maximum number of unique job names tabled by IAMSMFVS has been exceeded. SMF records that match the specified selection criteria but with job names other than those already tabled will be bypassed and not reported. System Action: Specify a MAXJOB value greater than nnnnn but less than or equal to32,000 and, if required, rerun the job. |
IAM621 | MAXDSN VALUE OF nnnn EXCEEDED - ADDITIONAL DATASET NAMES BYPASSED Explanation: The maximum number of unique data set names tabled by has been exceeded. Records that match the specified selection criteria but with data set names other than those already tabled will be bypassed and not reported or will be shown in a second report if present. System Action: Specify a MAXDSN value greater than nnnnn but less than or equal to 32,000 and, if required, rerun the job. |
IAM622 | MAXDSN VALUE OF nnnnn EXCEEDED - ADDITIONAL VSAM CLUSTER RELATIONSHIPS BYPASSED Explanation: IAMSMFVS issues a LOCATE for each ICF/VSAM DATA and/or INDEX component and adds the resulting cluster name to the tabled data set names. Those DATA and/or INDEX components that remain unrelated (I.E.: have not had the cluster name appended) when the value of MAXDSN is exceeded will be printed as unique data sets. System Action: ICF/VSAM clusters can take up to three (3) entries in the data set name table that is generated from the MAXDSN operand. If you only plan to extract information on ICF/VSAM clusters and you expect to have approximately 1000 clusters listed, specify a MAXDSN no less than 3000. If the error reoccurs, specify a MAXDSN value greater than nnnnn but less than or equal to 32,000 and, if required, rerun the job. |
IAM634 | SEQUENCE CHECKS FORCE SORTING OF DATA BEFORE IAM CREATION Explanation: The file recovery program found the records it was processing were not in ascending sequential order. An IAM file creation expects the IAM file to be loaded in order. The set of keys the recovery program is processing cannot be used as is to load an IAM file. The Independent Overflow records in an IAM file may not be in collating sequence. Recovery of a file with Independent Overflow could result in this message. System Action: The recovered records must be sorted before they can be used to load an IAM file. |
IAM635 | LOG AND IAM FILE ARE INCOMPATIBLE Explanation: The file recovery program found the log file records it was applying were not compatible with the IAM file it was rebuilding. System Action: The log file being applied and the IAM file in question should be checked to see if they actually represent the same data before attempting to continue with a file recovery. |
IAM636 | APPLY FAILED -- RECORD KEY FOLLOWS -- Explanation: The file recovery program found the record it was applying was not compatible with the IAM file it was rebuilding. System Action: The log file being applied and the IAM file in question should be checked to see if they actually represent the same data before attempting to continue with a file recovery. |
IAM637 | IAM INTERNAL BLOCK -- Explanation: The block shown contains file control information. System Action: None, information message only. |
IAM638 | IAM BLOCK NUMBER nnnnnn -- Explanation: The block shown is relative block number 'nnnnnn' in the file. System Action: None. This is an informational message only. |
IAM700 | Compuware Access Method Trace VER nnnnnnnn Date:yyyy.ddd Page:nnn |
IAM701 | DDNAME:ddname DSN:dataset name |
IAM702 | Type Time Request RPL/RBN PLH OPTCD RC/RINFO RECLEN Key |
IAM703 | ---- ---- ------- ------- --- ----- -------- ------ --- Explanation: IAM700 - IAM703 are headings for IAM trace output. |
IAM704 | Trace Ended Explanation: indicates the end of IAM tracing. |
IAM705 | There were trace lock failures Explanation: If any trace lock failures occurred during processing, this message will be issued. |
IAM710 | IOS 08.33.38.1900 PUT 00023A10 00040298 2040 01FE 00002D00 Explanation: This is the I/O Start trace detail line. The contents of each field are as follows: |
IAM711 | IOE 08.33.39.2200 PUT 00023A10 00040298 0000 01FE 0005A000 Explanation: This is the I/O End trace detail line. The contents of each field are as follows: |
IAM712 | BFR 08.33.39.2300 WRITE 00000026 00040298 1008 0005A1FE Explanation: This is the Buffer Manager trace detail line. The contents of each field are as follows: |
IAM713 | EXCP 08.33.39.2400 READ 00000024 00040298 0001 Explanation: This is the EXCP trace detail line. The contents of each field are as follows: |
IAM714 | XTND 08.34.02.0100 EXTEND 00000028 00000000 0102 0000 20980001 Explanation: This is the XTND trace detail line. The contents of each field are as follows: |
IAM715 | hh.mm.ss.nnnn PUT xxxxxxxx oooooooo rrrrrrrr llllllll kkkkkkkkkkkkkkkkkkkk Explanation: This is the file load detail trace line. The contents of each field are as follows: |
IAM716 | +kkkkkkkkExplanation: This is the continuation of the key of the record being processed, from the preceding IAM715 message. |
IAM998 | IAMSRORG(10.0.01/00P ) FDRREORG LICENSE VALIDATION FAILED, Explanation: The IAMSRORG program was unable to validate that the installation has a valid license for the FDRREORG product Version 5.4/85 or higher. This can occur if you do not have FDRREORG installed or you do not have the required version and level, or if FDRREORG is installed at the proper level it must be accessible either through the system link list, or through a JOBLIB or STEPLIB DD card. System Action: If you have the correct version available, make sure that it can be accessed by adding an appropriate JOBLIB or TESTLIB DD card with the proper load libraries specified. If you have an older version, you will need to upgrade it to more recent version. If you do not have the FDRREORG please contact BMC to obtain the product. |