Exactly.  Think back to the days before you had multiple systems
to change things from - or even back to before TSO/ISPF.  For 
example, if you had to enlarge a proclib how could you submit
a job to do so if it was in use by JES2 and JES2 was up in order
for you to submit (read in) a job.   You were able to make the
change because the NODSI attribute for HASJES20 in the PPT
for JES2.  For example, allocate a new proclib, copy old to new,
rename, then IPL or $PJES2,ABEND / restart.   No dynamic 
proclib support back then either.   But it was more than just
NODSI, even if you tried to override it, it didn't matter because
JES2 used S99NORES in the dynamic allocation. 

See a thread with subject "JES2 DD Concatenation issue" from
2008 with lots of information.  Brian Peterson authored a requirement
to allow DSI to be used for JES2 (HASJES20) in the PPT so PROCLIBs 
could be ENQed.  I forgot when that happened, but I've been running
that way for years.  

Paul, you even contributed to that thread with a job stream scenario 
to do the rename with the ENQs in place.   

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS       
mailto:[email protected]                                        
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/



>Maybe so, but JES2/HASP  has done this since day 1 (circa 1975).               
>        
>Many decisions made many moons ago are maintained for historical 
>compatability.        
>Those decisions would not necessarily be the same today.                       
>        
                                                                                
        
>><snip>                                                                        
>>        
>>No.  HSM will not migrate a file if it is open.  IIRC, But proclibs have      
>>        
 >>short usage.  So it is possible the proclib is not used within the           
 >>        
>>timeframe for migration is specified.  JES2 does not always open PROCLIBs     
>>        
>>after the TTRs are read into JES2 ASID.  Unless the environment has multiple  
>>        
 >>PROCxx statements in JES2 that are constantly used, PROC01 PROC02 etc, then  
 >>        
>>the dataset is not needed.  JES2 already knows where the data is located on   
>>        
>>the dasd volume.                                                              
>>        
>>>                                                                             
>>>         
>>>That breaks everything that ought to be a rule.  JES2 should be a 
>>>law-abiding        
>>>citizen and hold the data set open.                                          
>>>        
                                                                                
        
>>>-- gil                                                                       
>>>        
>>></snip>                                                               

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to