Kees,

This environment also was in a non-SMS environment and the STK silo (SLS8500).  
I will check further into the logic.  The LIBNAME is correct.  I will keep on 
digging.

Thanks.
--------------------------------------------
On Wed, 11/11/15, Vernooij, CP (ITOPT1) - KLM <kees.verno...@klm.com> wrote:

 Subject: Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF 
DATA SET
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 11 November, 2015, 2:21 AM
 
 John,
 
 At first sight: no, this should do. 
 I had to add the check for
 &UNIT='AFF=SMST', but we came from an STK Silo,
 where the volumes are nog SMS managed and in the VSM they
 were SMS managed if I recall correctly.
 
 You can check the logic in the SC routine, to
 see if an SC is assigned before it comes to this WHEN
 clause. Or other SELECT clauses following it. Furthermore,
 is the libname correct, i.e. is the same SC assigned when
 the JCL specifies UNIT=3490?
 
 Kees.
 
 -----Original Message-----
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John Dawes
 Sent: 10 November,
 2015 18:03
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: JCL QUESTION :IGD17045I SPACE NOT
 SPECIFIED FOR ALLOCATION OF DATA SET
 
 Kees,
 
 I took a
 look at the SC routine and this is what I found:
 
 /* CHECK FOR AFFINITY AND
 STACKED VOLUMES                      
 /**************************************************************
                                
                                
     WHEN ( &UNIT='AFF=SMST' OR
 &ANYVOL='REF=ST' )              
     DO                         
                                
           IF &STORCLAS NE ''
 THEN                              
           SET &STORCLAS =
 &STORCLAS                            
           ELSE DO               
                               
                   SELECT         
                              
                        WHEN
 (&LIBNAME = 'SHSMF')            
                         SET
 &STORCLAS = 'SCSMF'             
                        WHEN
 (&LIBNAME = 'SHVTS')            
                         SET
 &STORCLAS = 'SCVTS'       
 
 ..etc....etc. etc.
 
 In your example you have a
 FILTLIST built but in this ACS routine there is none.  In
 your view do I need to build the FILTLIST?
 
 
 
 --------------------------------------------
 On Tue, 10/11/15, Vernooij, CP (ITOPT1) - KLM
 <kees.verno...@klm.com>
 wrote:
 
  Subject: Re: JCL
 QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF
 DATA SET
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Tuesday, 10 November, 2015, 10:27
 AM
  
  Check you ACS
 routines. 
 I have the following filtlist to
 recognize an allocation of tape devices. I remember having
 to add the AFF string for the same purpose when moving from
 Storage Tek (then Sun, then Oracle) to TS7740 libraries:
 
 FILTLIST UNIT_VTS 
    INCLUDE('TS7740',   
                              
 'AFF=SMST', 
                
               '3480',     
                              
 '3490',     
        
                       'TAPE', 
    
                    
           'TAPE2')    
 
 Kees. 
  -----Original
 Message-----
  From: IBM Mainframe Discussion
 List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
  On Behalf Of John Dawes
  Sent:
 10 November,
  2015 16:19
 
 To: IBM-MAIN@LISTSERV.UA.EDU
  Subject: JCL QUESTION :IGD17045I SPACE NOT
  SPECIFIED FOR ALLOCATION OF DATA SET
  
  G'Day 
 
 
  I
  have a problem with
 allocating a dsn to tape.  This problem
 
 started when we transferred from Oracle VSM to IBM VTS. 
  
  
  The error
 message is as
  follows:
  
  IEF344I MVRXL#JP
  TSO CUMUL
 OUTPUT01 - ALLOCATION FAILED DUE TO DATA FACILITY
  SYSTEM ERROR
  IGD17045I SPACE
 NOT SPECIFIED
  FOR ALLOCATION OF DATA SET 
                  
     
  SYSCICS.CICS.CICSVP.G0005V00   
     
  
  This
 job has
  been running without any problem
 when it was allocated under
  VSM however
 with the switch to VTS the abends have occurred
  due to the AFF parm.
  
  Below
  is the jcl:
  
  //ACUMUL  EXEC
  IKJEFT01,                     
  
     
  //       
  
     PARM=('CICSAPP')     
        
      
  //* 
                    
         
                  
  //STEP1  DD
  DISP=(SHR,PASS),DSN=&&CLIST     
     
  //CICSLIST DD
  DSN=&&LISTCICS,DISP=(SHR,DELETE)   
   
  //SYSTSPRT DD SYSOUT=*           
    
              
 
 //SYSPRINT DD SYSOUT=* 
             
               
  //SYSTSIN  DD
 DUMMY                 
         
      
  //*       
 
                                    
     
  //A3490    DD 
  UNIT=(3490,,DEFER)             
    
  //OUTPUT01 DD
 DSN=SYSCICS.CICS.CICSVP(+1), 
  //       
     DISP=(NEW,CATLG,DELETE), 
       
     
  //           
 
 DCB=MODDSCB,                        
  //            RECFM=VB,LRECL=32756, 
  
             
  // 
        
   
 UNIT=AFF=A3490,LABEL=EXPDT=99000    
  
  As a temporary workaround I
 
 have removed the AFF parm (UNIT=3490,LABEL=EXPDT=99000)
  however because of JCL changes that would need
 to be done
  which the user would like to
 avoid can something else be
  done?
  
  Please note that NO
  SMS changes have been done since 2013 even
 though the error
  message points out to a
 SMS problem.
   
  Thanks.
 
  
  
  //* 
                
             
                  
  
 
 ----------------------------------------------------------------------
  For IBM-MAIN subscribe / signoff / archive
  access instructions,
  send
 email to lists...@listserv.ua.edu
  with the message: INFO IBM-MAIN
 
 ********************************************************
  For information, services and offers,
 please
  visit our web site: http://www.klm.com. This e-mail and
 any
  attachment may contain confidential and
 privileged material
  intended for the
 addressee only. If you are not the
 
 addressee, you are notified that no part of the e-mail or
  any attachment may be disclosed, copied or
 distributed, and
  that any other action
 related to this e-mail or attachment
  is
 strictly prohibited, and may be unlawful. If you have
  received this e-mail by error, please notify
 the sender
  immediately by return e-mail,
 and delete this message. 
  
 
 Koninklijke Luchtvaart
  Maatschappij NV
 (KLM), its subsidiaries and/or its employees
  shall not be liable for the incorrect or
 incomplete
  transmission of this e-mail or
 any attachments, nor
  responsible for any
 delay in receipt. 
  Koninklijke Luchtvaart
 Maatschappij N.V. (also
  known as KLM Royal
 Dutch Airlines) is registered in
 
 Amstelveen, The Netherlands, with registered number
  33014286
 
 ********************************************************
              
  
  
 
 ----------------------------------------------------------------------
  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 information, services and offers, please
 visit our web site: http://www.klm.com. This e-mail and any
 attachment may contain confidential and privileged material
 intended for the addressee only. If you are not the
 addressee, you are notified that no part of the e-mail or
 any attachment may be disclosed, copied or distributed, and
 that any other action related to this e-mail or attachment
 is strictly prohibited, and may be unlawful. If you have
 received this e-mail by error, please notify the sender
 immediately by return e-mail, and delete this message. 
 
 Koninklijke Luchtvaart
 Maatschappij NV (KLM), its subsidiaries and/or its employees
 shall not be liable for the incorrect or incomplete
 transmission of this e-mail or any attachments, nor
 responsible for any delay in receipt. 
 Koninklijke Luchtvaart Maatschappij N.V. (also
 known as KLM Royal Dutch Airlines) is registered in
 Amstelveen, The Netherlands, with registered number
 33014286
 ********************************************************
             
 
 
 ----------------------------------------------------------------------
 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

Reply via email to