30.01.2015 Views

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MESSAGES AND CODES<br />

MESSAGES FROM <strong>FDR</strong>, DSF, AND ABR (<strong>FDR</strong>NNN) 100.3<br />

Action:<br />

UNIT=uuuu PROCESSING BYPASSED -- ONLINE DEVICE WITH LONG TERM<br />

RESERVE – The unit address “uuuu” being processed was attempted, but<br />

found to be in use for over 10 seconds. The CHKONLRESERVE option can<br />

be to set the desired processing when long term reserves are encountered.<br />

If the condition is one that can be corrected, correct it and resubmit the job. If needed,<br />

call INNOVATION DATA PROCESSING technical support for assistance.<br />

<strong>FDR</strong>421 type LOCATE ERROR -- description -- DSN=dsname<br />

Reason: 1. A Catalog LOCATE SVC was issued requesting identification of the VSAM component or<br />

SMS managed data set named by “dsname”. The LOCATE either failed or returned a<br />

component type or cluster name description that is not currently handled.<br />

2. An error was found in the VVDS.<br />

“description” can be:<br />

RETURN CODE rc -- REASON IGGOCLaa-crs – The LOCATE failed. The error<br />

codes are documented in the IBM System Messages manual under<br />

message number IDC3009I.<br />

ENTYPE - c(X'xx') - entrytype – The program encountered a type of component<br />

entry that it does not presently support.<br />

NAMEDS - c(X'xx') - entrytype – The program encountered a type of cluster entry<br />

that it does not presently support.<br />

NO MATCHING VVR – ICFSOURCE=VVDS – A VSAM data set does not have a<br />

VVR in the VVDS (orphan DSCB). (See Note below.)<br />

NO MATCHING NVR – SMSSOURCE=VVDS – A non-VSAM data set on an<br />

SMS-Managed volume does not have an NVR in the VVDS (orphan<br />

DSCB). (See Note below.)<br />

MULTIPLE VVRS (nn) ON VOLUME vvvvvv – A VSAM component has “nn” VVRs<br />

in the VVDS.<br />

MULTIPLE NVRS (nn) ON VOLUME vvvvvv – A non-VSAM data set has “nn”<br />

NVRs in the VVDS of SMS-Managed volume “vvvvvv”.<br />

For any other description, an error exists in the catalog.<br />

NOTE: Orphan DSCBs are detected only if the <strong>FDR</strong>EPORT option DIAGNOSEVVDS is<br />

enabled.<br />

Action: This is only a warning message. The program does not associate the component shown<br />

by DSN= with a cluster name, or attempts to recover from the VVDS error and<br />

processing continues. If possible, correct the error and re-run.<br />

In some cases, the program may display a jobstream that you can use to correct the<br />

error. If you request the PUNCHDIAGNOS option, this jobstream is written to a data<br />

set, specified by DDname DIAGPCH.<br />

<strong>FDR</strong>422<br />

Reason:<br />

<strong>FDR</strong>424<br />

Action:<br />

Reason:<br />

DDNAME=ddname REFERENCES DATA SET CURRENTLY IN USE--DSNAME=dsname<br />

The data set described by the message is being accessed from another task or address space.<br />

Rerun job when file is available for processing.<br />

PROCESSING OF VOLUME SERIAL NUMBER vvvvvv COMPLETED-- nnnn DATA SETS UPDATED<br />

<strong>Processing</strong> of volume “vvvvvv” completed. “nnnn” Format 1 DSCBs were changed (this<br />

includes the ABR Model DSCB if appropriate).<br />

<strong>FDR</strong>425 NOT REFERENCED DURING EXECUTION-- description<br />

Reason: Identifies a statement or operand for which no matching volumes or data sets were<br />

found during this execution.<br />

Action: Verify all control statements are correct. This control statement did not affect the<br />

execution. Results may not be what were expected. Examine output carefully!<br />

CHAPTER 100 – PAGE 100-84 –

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!