Yes indeed. The DSNames would not be those of the original DDDEFs, but
of the UCLIN REP[laced] ones - after a cloned CSI has been updated to
point at them.
 
E.g.
 
 //SMPCNTL  DD *                                                        
  SET BOUNDARY(GLOBAL)                                                  
  .                                                                     
  UCLIN                                                                 
  .                                                                     
  REP     DDDEF(SMPPTS)                                                 
          DA(<whatever the cloned SMPPTS new HLQ
is>.SMPPTS)                                   
          SHR                                                           
  .                                                                     
  DEL     DDDEF(SMPLOG)                                                 
  .                                                                     
  ADD     DDDEF(SMPLOG)                                                 
          SYSOUT(*)                                                     
  .                                                                     
  ENDUCL                                                                
  .
 
<etc.>
 
                                                                     

On 10/08/2017 00:58, Edward Gould wrote:
>> On Aug 9, 2017, at 4:34 PM, Paul Gilmartin 
>> <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>>
>> On Wed, 9 Aug 2017 20:58:11 +0100, CM Poncelet wrote:
>> ——————————————SNIP----------------------------------------------
>> If the DSNames are in DDDEFs (highly recommended) they can be listed
>> with SMP/E commands.  At times, a question has been posed here,
>> "Can I, for a one-off, overide in JCL the DDDEFs in the CSIs?"  Yes, but
>> don't do that!
> Gil,
>
> I have a preference to use JCL with dd’s in the step(proc) for maintenance.
>
> I have been burned by a fellow sysprog as he managed to put the maintenance 
> in the wrong zone. 
>
> After the IPL I started to get the phone calls saying that X is still broken. 
> The time it takes is a PITA. I then have to track down what went where.
> I also get a black mark from the programmers and my boss for screwing it up. 
> The black mark from the programmers is aggravating as then they stop trusting 
> me and I have to earn their trust back. The boss is not so forgiving even 
> when a 3rd person is involved. His answer is your fault as you didn’t verify 
> what the person did. Personally I don’t have the time in the day/evening to 
> check out what fellow sysprogs did. About 20 years ago I was putting in 100 
> hour work weeks and it burned me out.
> Once I figure out what happened, that means paper work and another scheduled 
> IPL. 
> I can *TRUST* JCL and not worry about the DDEF’s which are for all intents 
> purposes is invisible.
>
> Ed
> ----------------------------------------------------------------------
> 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