hi Lim, my advise would be to add some TEMP datasets within the JCL... you can hardcode the Volser with a disp of Delete, Delete. this util allocates space from TEMP as defined in SMS and remove after the success..
thanks, Amit On Tue, Sep 13, 2011 at 5:59 AM, Lim Ming Liang <[email protected]> wrote: > Hi Bill, > Much obliged on the updates. > Regards Lim ML > > > On 13/09/11 1:24 AM, Bill Godfrey wrote: > >> GIMUNZIP might be trying to allocate a Large Format sequential data set >> (DSNTYPE=LARGE) rather than a PDSE. I say that because at this web page: >> https://www-304.ibm.com/**support/docview.wss?uid=**isg1IO10377<https://www-304.ibm.com/support/docview.wss?uid=isg1IO10377> >> it says: >> "GIMUNZIP has been updated to allocate SYSUT1 as a Large Format sequential >> data set." >> >> Large Format data sets, like PDSEs, cannot be on VIO. I suspect that the >> error code 0C060090 might apply to both PDSEs and Large Format data sets, >> even though the manual describing the error code only mentions PDSEs. But I >> am not certain of that. >> >> I don't know what unit name GIMUNZIP uses, if any, in this allocation, and >> I don't know if temporary data set allocations are being controlled by ACS >> routines on your system. If they are, the logic that allows VIO for >> temporary data sets might need to check for&DSNTYPE equal to LARGE and not >> include VIO for such allocations. That's assuming this actually is a Large >> Format data set allocation. >> >> Bill >> >> On Sun, 11 Sep 2011 11:26:41 +0800, Lim Ming Liang<[email protected]> >> wrote: >> >> Hi Bill, >>> "PDSE cannot be VIO" , is it a DFSMSdfp software constraint ? >>> >>> "GIMUNZIP is trying to allocate a PDSE on VIO for SYSUT1" , is it an >>> software action taken by GIMUNZIP to dynamically allocate SYSUT1 with VIO >>> ? >>> >>> Or is it my system setup for VIO allocation causing the problem ? >>> >>> Pardon me, I am still trying to digest those stuff you provided me. >>> >>> Thank you. >>> Regards Lim ML >>> >>> On 11/09/11 1:46 AM, Bill Godfrey wrote: >>> >>>> Google for 0C060090,which is in one of the messages. It will take you >>>> here: >>>> >>>> http://www.mail-archive.com/**[email protected]/msg28790.**html<http://www.mail-archive.com/[email protected]/msg28790.html> >>>> >>>> which shows an ibm-main post from 2006 that says: >>>> >>>> (quote) >>>> HISTORIC RETURN CODE IS 196 DIAGNOSTIC INFORMATION IS 0C060090 >>>> For this code you need to look in the DFSMSdsp Diagnostic Reference. You >>>> will find that, for CREATE, 0C060090 means >>>> PDSE cannot be VIO. >>>> (end quote) >>>> >>>> This is confirmed here in the DFSMSdfp Diagnosis manual: >>>> >>>> http://publibz.boulder.ibm.**com/cgi-bin/bookmgr_OS390/** >>>> BOOKS/DGT2R190/6.9.1<http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2R190/6.9.1> >>>> >>>> So gimunzip is trying to allocate a PDSE on VIO for SYSUT1. >>>> >>>> Maybe that information will help solve the problem. >>>> >>>> Bill >>>> >>>> On Sun, 11 Sep 2011 00:47:39 +0800, Lim Ming Liang<[email protected]> >>>> wrote: >>>> >>>> That description not really fit the problem I am having here. >>>>> I googled and found an archived back in Feb did talked about this >>>>> messages I am having, and the resolution is add volume parameter in the >>>>> ARCHDEF. >>>>> Yes, it did help to get the job going, but I wonder wh., All those >>>>> extracted Data Sets are pre-allocated and cataloged, and why GIMUNZIP >>>>> need the volume parameter to be specified ? >>>>> Regards Lim ML >>>>> >>>>> On 10/09/11 9:37 PM, Bill Johnson wrote: >>>>> >>>>>> Check this:https://www-304.ibm.com/**support/docview.wss?uid=** >>>>>> isg1IO10377<https://www-304.ibm.com/support/docview.wss?uid=isg1IO10377> >>>>>> >>>>>> On Sat, Sep 10, 2011 at 9:25 AM, Lim Ming Liang<[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> Hi, >>>>>>>> I run GIMUNZIP, >>>>>>>> >>>>>>>> ----------<GIMUNZIP> >>>>>>>> ----------<ARCHDEF >>>>>>>> ---------- archid="AAOPEXEC.100" >>>>>>>> ---------- newname="TRX4.AOP.AAOPEXEC" >>>>>>>> ---------- /> >>>>>>>> >>>>>>>> and encountered error messages; >>>>>>>> >>>>>>>> ** ALLOCATION FAILED FOR SYSUT1 - IKJ56893I FILE SYSUT1 NOT >>>>>>>> ALLOCATED+. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - IGD17040I ERROR IN >>>>>>>> DADSM >>>>>>>> PROCESSING ON VOLUME UNKNWN FOR DATA SET. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - >>>>>>>> SYS11253.T114250.RA000.** >>>>>>>> IBMUSERF.R0100060. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - HISTORIC RETURN >>>>>>>> CODE IS 196 >>>>>>>> DIAGNOSTIC INFORMATION IS 0C060090. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - IGD306I UNEXPECTED >>>>>>>> ERROR >>>>>>>> DURING IGGDAC02 PROCESSING. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - RETURN CODE 12 >>>>>>>> REASON CODE >>>>>>>> 144. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - THE MODULE THAT >>>>>>>> DETECTED THE >>>>>>>> ERROR IS IGDVTSDA. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - SMS MODULE TRACE >>>>>>>> BACK - VTSDA >>>>>>>> VTSCR SSIRT. >>>>>>>> GIM54701S ** ALLOCATION FAILED FOR SYSUT1 - SYMPTOM RECORD >>>>>>>> CREATED, >>>>>>>> PROBLEM ID IS IGD00000. >>>>>>>> GIM47800S ** AN ERROR OCCURRED WHILE GIMUNZIP WAS PROCESSING >>>>>>>> ARCHIVE >>>>>>>> AAOPEXEC.100. >>>>>>>> GIM20501I GIMUNZIP PROCESSING IS COMPLETE. THE HIGHEST >>>>>>>> RETURN CODE WAS >>>>>>>> 12. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Is this something to do with SMS setup? Please help. >>>>>>>> -- >>>>>>>> Regards Lim ML >>>>>>>> >>>>>>> ------------------------------**------------------------------** >> ---------- >> 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<http://bama.ua.edu/archives/ibm-main.html> >> >> > ------------------------------**------------------------------**---------- > 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<http://bama.ua.edu/archives/ibm-main.html> > ---------------------------------------------------------------------- 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
