Debbie,

All  good suggestions.

What I typically do is browse the data set in the linklst the member (module) 
resides.  I first look to make sure there are no extents.  I will allocate 
datasets in the linkst with primary and no seconday.

Next in the data set I sort on TTR and see if the module having a problem is 
located at a large TTR location.  That usually means it has been recently 
moved/lked into that data set.  Especially if it is farther out then the next 
to last module.

Member                               Size       TTR
Name

READWRT                            00000210   00091D  
DAFN                               00030A38   000A05  
AFCLOGR1                           00000AF0   000E05  
SP1UT017                           00002B90   000F04  
ANNOTATX                           00000CB8   000F0C  
XSTAT02A                           000015D0   000F14  

>From this brief list you can see all of my modules are located close to the 
>correct TTR for the size of the module.  However, I know immediately that 
>XSTAT02A has been recently added to this data set because it is the last in 
>the TTR list.

Just a couple of thoughts to help you isolate your problem.

If your dataset in the linklst that has the module has gone into extents, I do 
not think an LLA Refresh will work.  I think you either IPL or have to rebuild 
the Lnklst.

Another option would be to move the modules into a higher up Lnklsted data set 
that has room and LLA Refresh   That could hold you till your next IPL.

I will place a dummy, large empty PDS at the top of the LNKST just for such 
emergencies.  It is emptied prior to an IPL so the correct module is accessed 
further down.

Lizette

>
>I am having various abends (S0c1, S0c4) with modules accessed through a
>linklisted library.  The library itself appears to be fine.  If I steplib to
>the library instead of accessing it through the linklist, my job runs
>without issue.  I have recycled both LLA and VLF and still have the same
>problem.
>
>Any clues where else I can look?
>
>My next step is going to be to remove the offending library from linklist
>and re-add it.  If I still fail I will be removing it and adding a different
>library which contains the same modules.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to