Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Getting "deferred roll in" messages for non-gdg fi

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
st06rlr

New User


Joined: 16 Mar 2006
Posts: 2
Location: Ohio

PostPosted: Fri Mar 17, 2006 12:07 am    Post subject: Getting "deferred roll in" messages for non-gdg fi
Reply with quote

Greetings,

We have been recieving warning messages in IDCAMS DIAG catalog output. These messages indicate that a file is in a DEFERRED ROLL IN STATE. The problem with this is that the files in question are not GDG. I have attempted to correct this with IDCAMS ALTER ROLLIN. It fails because they are not GDG.

Has any one seen this before? If so, how is it fixed?

Thanks

Example:Error message from IDCAMS diagnose IDFCAT
IDC01380I GENERATION DATA SET FOUND IN DEFERRED ROLL IN STATE
IDC01380I ATM.CHKPOINT.TIMEOUT


Quick reference output for IDC01280I
IDC01380I GENERATION DATA SET FOUND IN DEFERRED ROLL IN STATE

Explanation: It is an informational message only. Comparison of GDs is
deferred and roll in state and catalog recording continues.

Detecting Module: IDCDA01


Information on file.
TSO listc entries('ATM.CHKPOINT.TIMEOUT') all
NONVSAM ------- ATM.CHKPOINT.TIMEOUT
IN-CAT --- CATALOG.ICF1.PROGPROD.DATA
HISTORY
DATASET-OWNER-----(NULL) CREATION--------1996.191
RELEASE----------------2 EXPIRATION------0000.000
ACCOUNT-INFO-----------------------------------(NULL)
STATUS----------DEFERRED
SMSDATA
STORAGECLASS ----STORAGE MANAGEMENTCLASS----MIG45
DATACLASS --------(NULL) LBACKUP ---2006.071.1848
VOLUMES
VOLSER------------STR008 DEVTYPE------X'3010200F'
FSEQN-----------------0
ASSOCIATIONS--------(NULL)
ATTRIBUTES
***
Back to top
View user's profile Send private message

st06rlr

New User


Joined: 16 Mar 2006
Posts: 2
Location: Ohio

PostPosted: Mon Mar 20, 2006 8:29 pm    Post subject: Re: Getting "deferred roll in" messages for non-gd
Reply with quote

Found this information on IBM's web site when I did a search on IDCDA01 the detecting module.

Problem
Prior to the application of the PTFs for OW51458, there is the possibility that NON GDG data sets may be set to DEFERRED ROLLIN STATUS. This is incorrect as only GDG's should have the possibility of being in DEFERRED ROLLIN STATUS. OW51458 corrects a problem with renaming a data set when the rename fails, usually due to a security failure.


Solution
To correct this condition, the data set must be on a dasd volume. If the data set has been migrated, then it needs to be recalled to dasd volume (and not a ML1 volume). If you cannot recall the dataset, then recovering from a backup is required. The following samples assume the data set name that is incorrectly marked as being in deferred rollin status is named IBM.PROD.LOADLIB.
If the data set has been migrated by DFHSM, then try recalling it to a dasd volume. If you are unable to recall the data, then use DFHSM to recover the data set to another name for example IBM.PROD.LOADLIB.RECOVER.

Assuming you were able to recall the data set to a dasd volume, then issue the following IDCAMS commands:

LISTCAT ENT(IBM.PROD.LOADLIB) ALL

**** Note that you will need some of the information from the listcat issued above****

DELETE NONVSAM IBM.PROD.LOADLIB NOSCRATCH

**** Note the above will delete the catalog entry, but leave the data set on the volume ****

DEFINE NONVSAM (NAME(IBM.PROD.LOADLIB) -

RECATALOG VOLUMES(XXXXXX) DEVICETYPES(3390)) **** Replace the value XXXXXX with the volser from the LISTCAT command you issued above. If your dasd type is 3390 then the above is correct. If the device type is 3380 then replace 3390 with 3380, If the device type is 9345 then replace 3390 with 9345. To determine the device type refer to the LISTCAT you issued above. If the DEVTYPE is 3010200F then the devicetype is 3390. If the DEVTYPE is 3010200E then the devicetype is 3380. If the DEVTYPE is 30102004 then the devicetype is 9345. ****


If you cannot use DFHSM recall and will be using DFHSM recover instead to recover the data set to a different name then issue the following IDCAMS commands using the above example data set name:

LISTCAT ENT(IBM.PROD.LOADLIB.RECOVER) ALL
**** Note this command should be issued against the recovered data set with the new name so we what the various attributes are ****

DELETE NONVSAM IBM.PROD.LOADLIB PURGE
**** Note this should be issued against the original data set, not the recovered data set ****
ALTER IBM.PROD.LOADLIB.RECOVER -
NEWNAME(IBM.PROD.LOADLIB)
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
This topic is locked: you cannot edit posts or make replies. Extract all "IF" Statements... Adarsh Damodaran CLIST & REXX 1 Wed Sep 06, 2017 9:28 am
No new posts Changeman get multiple "Browse C... elixir1986 Compuware & Other Tools 4 Fri Jul 14, 2017 1:48 am
No new posts Include/omit with "ALL" pa... mgl DFSORT/ICETOOL 6 Wed Jun 14, 2017 2:31 pm
No new posts READ A PACKED "NEGATIVE" FI... jdesouza CA Products 3 Tue May 02, 2017 11:43 pm
No new posts RC 20 for Address ISPEXEC "ISRED... pkmurali CLIST & REXX 3 Sun Apr 16, 2017 11:30 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us