This is what I have.  In the Data set name type   ===>          it is blank as 
shown below.

Data set name  ===> ''SYS2.BATCH.JOBS.OUTPUT'                                   
 
Member to use  ===> JOB06703                                                 
Disposition    ===> SHR        (OLD, NEW, SHR, MOD)                           
                                                                              
Management class     ===>           (Blank for default management class)      
Storage class        ===>           (Blank for default storage class)         
  Volume serial      ===>           (Blank for authorized default volume)     
  Device type        ===>           (Generic unit or device address)          
Data class           ===>           (Blank for default data class)            
  Space units        ===> CYLS      (BLKS, TRKS, CYLS, BY, KB, or MB)         
  Primary quantity   ===> 1         (In above units)                          
  Secondary quantity ===> 5         (In above units)                          
  Directory blocks   ===>           (Zero for sequential data set)            
  Record format      ===> VBA                                                 
  Record length      ===> 240                                                 
  Block size         ===> 3120                                                
Data set name type   ===>           (LIBRARY, blank, ... See Help for more)   
Extended attributes  ===>           (NO, OPT, or blank)                       

--------------------------------------------
On Fri, 4/29/16, Richards, Robert B. <robert.richa...@opm.gov> wrote:

 Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Friday, April 29, 2016, 7:50 AM
 
 Data set name  ===>
 'ABCDE.FGHIJK.LMNOP'                     
         
 Member to use  ===>
 QRSTUV                                   
            
 Disposition   
 ===> NEW        (OLD, NEW, SHR, MOD)           
            
            
                                        
                       
 Management
 class     ===>       
    (Blank for default management class)  
 Storage class              ===>   
         (Blank for default storage class) 
    
   Volume serial       
    ===>           (Blank for
 authorized default volume) 
   Device type 
             ===>           (Generic
 unit or device address)      
 Data
 class                  ===>       
    (Blank for default data class)        
   Space units              ===>
 CYLS   (BLKS, TRKS, CYLS, BY, KB, or MB) 
    
   Primary quantity 
    ===> 25        (In above units)     
                 
   Secondary
 quantity ===> 5          (In above units)       
               
   Directory blocks 
    ===> 45        (Zero for sequential
 data set)     <===== Did you specify
 directory blanks???   
   Record
 format       ===> FBA               
                              
   Record length        ===> 133     
                                    
    
   Block size         
      ===>                       
                          
 Data set name type  ===>       
    <======= Do you have this value
 specified???
 Extended attributes  ===> 
          (NO, OPT, or blank)           
        
 
 -----Original Message-----
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of willie bunter
 Sent: Friday,
 April 29, 2016 7:45 AM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM
 SDSF
 
 Lizette,
 
 I tried your suggestion using
 NEW but it doesn't work.  I get the message MEMBER NAME
 NOT ALLOWED
 
 I hit the PF1
 option but it wasn't much help.   
 --------------------------------------------
 On Thu, 4/28/16, Lizette Koehler <stars...@mindspring.com>
 wrote:
 
  Subject: Re: SAVING
 JOB OUTPUT IN A PDSE FROM SDSF
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Thursday, April 28, 2016, 7:08 PM
  
  When you use XDC and NEW
  it will indicate if the member already
 exists.
  
  You should try
 this and see if
  it works.
 
 
  I find trying
  SHR, OLD
 and NEW on  a PDS that will not matter if it is  over
 written a good thing to try to understand how things 
 work.
  
  Also, you could
 press
  PF1 (HELP) and see what the HELP
 panel states.
  
  Lizette
  
  
  >
 -----Original Message-----
  > From: IBM
 Mainframe Discussion List
  [mailto:IBM-MAIN@LISTSERV.UA.EDU]
  On
  > Behalf Of willie
 bunter
  > Sent: Thursday, April 28, 2016
 4:00 PM  > To: IBM-MAIN@LISTSERV.UA.EDU 
 > Subject: SAVING JOB OUTPUT IN A PDSE FROM  SDSF 
 >  > Hallo  All,  >  > I need your 
 suggestions.  I am savings job output in a PDSE using 
 SDSF.  The  > member name I use is the  job number
 e.g.
  > Member to use  ===>
  JOB067XX
  >
  > I am
  afraid that some
 where down the line I could overwrite a  member because 
 > the job number could be  the same.  Is there
 something I could do to prevent  > this from
 happening?
  >
  
  > Below is an example of the screen when 
 I type XDC beside the job:
  >
  > Data set name  ===>
 
 'SYS2.BATCH.JOBS.OUTPUT
  > Member
 to
  use  ===> JOB06703
 
 > Disposition
  ===> SHR       
 (OLD, NEW, SHR, MOD)
  >
 
 > Thanks in
  advance.
 
 > 
  
 
 ----------------------------------------------------------------------
  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

Reply via email to