Garth, I modified the SC ACS routine so as to exclude the GUASPACE however I got the same result. What I think is if a CATALOG existed on a non-SMS volume and then placed on a SMS manged volume the OBJECT & VOLUME parms is required. I ran another test. I allocated a CATALOG on a non-sms volume. Next I did the EXPORT to a SMS volume, I then allocated on a SMS volume (not guaranteed space ) and tried the IMPORT. The job failed with the same error code. I then added the OBJECT & VOLUME parms and reran the step and it worked. This leads me to believe that when allocating a CATALOG on a SMS volume (which used to be on a non-SMS managed volume) the OBJECT & VOLUME parms is required if performing an IMPORT. Perhaps somebody can correct me if I am wrong.
________________________________ From: Darth Keller <darth.kel...@assurant.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, February 12, 2013 8:30:44 AM Subject: Re: UNABLE TO IMPORT - IGD17802I Willie - I don't think it was a fluke that it worked. I think it worked as designed. I think that you need to look at the SMS constructs assigned to the catalog when it was being allocated without your OBJECT(VOLUMES statement as it appears to me the Guaranteed Space attribute was what was biting you. With what you were trying to accomplish, going to from non-SMS to SMS, OBJECTS(VOLUMES was required. This is a case, I think, where well placed WRITE statements in your SMS routines would help you understand what's going on. ddk From: willie bunter <williebun...@yahoo.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/11/2013 03:47 PM Subject: Re: UNABLE TO IMPORT - IGD17802I Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Darth, I am not sure if you saw my earlier post. I think the problem is fixed. This is what I did. IMPORT IDS(SYS1.ZWA6PWG.BKUP) - ODS(CATALOG.DB2TESX) - OBJECTS(CATALOG.DB2TESX - VOLUMES(DB2AP1))) - IDC0233I TOO MANY RIGHT PARENTHESES FOUND. EXCESS IGNORED ALIAS - LOCK - INTOEMPTY IDC0604I DATA SET BEING IMPORTED WAS EXPORTED ON 02/11/13 AT 10:02:09 IDC01653I ALIASES FROM THE PORTABLE DATA SET WERE DEFINED COCO SOSO LOLO DODO ZOZO YOYO I still don't understand why the problem happened. Is it because moving a CATALOG from a non-SMS volume to a SMS volume isn't as straight forward as it may appear. Are the OBJECTS & VOLUMES PARM needed when performing this? Perhaps it was a fluke it worked? ________________________________ From: Darth Keller <darth.kel...@assurant.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, February 11, 2013 1:11:49 PM Subject: Re: UNABLE TO IMPORT - IGD17802I From the manual: If you select OUTDATASET, the VSAM data set you identify is dynamically allocated. So I think you're getting interference from your SMS routines. You may want to specify the STORAGECLAS & MGMTCLAS parameters on your IMPORT cmmd also. Do you have any IGD* messages beside what you've shown to indicate what SMS is doing? Do you have any WRITE statements in your routines? ddk From: willie bunter <williebun...@yahoo.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/11/2013 09:30 AM Subject: UNABLE TO IMPORT - IGD17802I Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Good Day To All Readers, I am having a problem trying to perform the IMPORT. Here is the error message : IMPORT IDS(SYS1.ZWA6PWG.BKUP) - ODS(CATALOG.DB2TESX) - ALIAS - LOCK - INTOEMPTY IDC0604I DATA SET BEING IMPORTED WAS EXPORTED ON 02/11/13 AT 10:02:09 IGD17802I VOLUMES SPECIFIED BY THE CALLER ARE NOT IN THE SAME STORAGE GROUP FOR A GUARANTEED SPACE REQUEST, DATA SET IS CATALOG.DB2TESX IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET CATALOG.DB2TESX IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 I verified that the volumes in the SG are in the correct storage group. The error message indicates that it is not the case. Would the error be caused because the IMPORT dsn is on a non-SMS managed volume? I would greatly appreciate your advice. Thanks. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN