Hi,

We had a production job that was canceled after 8 hours in the machine, 
during month end processing.

Here is what the job was doing :

DUMP DATASET(INCLUDE(HW*.**)                                        
             BY((DSORG NE VSAM))                                    
             EXCLUDE(HWAT.**,HW%C.**,HW%D.**,HW%I.**,HW%Q.**,       
                     HW%S.**,HW%U.**,HW%V*.**,HW%Z.**,**.TEMP.**,   
                     **.EDWXTRCT.**,**.TEMP%,HWP.HWPEIDCM.EA*.**,   
                     HWF.FEDOFF.**,HWF.HWFFSORT.**,HWF.HWFISORT.**, 
                     HWF.HWFFIDCM.HWFF5*.**,HWF.HWFIIDCM.FTO*,      
                     HWF.HWFI598P.**,HWF.HWFI600P.**,               
                     HWL.HWLV740P.IRSREPT*,HWL.HWLVF%P.IPREOFF*,   -
                     HWL.HWLVF35P.**,HWJ.HWJEIDCM.BKUP.**))         
     OUTDDNAME(OFFSITE,ONSITE)                                      
     TOLERATE(ENQF) OPTIMIZE(4)                                     
     CONCURRENT SHARE SPHERE    

Summary:

We did receive CA Sysview warning messages for this job as follows :

 
23:42:30.05 P1 S2279 00000094  GSVX321W (MVSDATA) Threshold JOB 
JOBIOR HWGGBK2P PROBLEM V=210.7 W=75.00
                                                                   P=100.0 
00:00:30.08 P1 S2279 00000094  GSVX321W (MVSDATA) Threshold JOB 
JOBIOR HWGGBK2P  PROBLEM V=249.5 W=75.00
                                P=100.0                                         
 
Conclusion :

Would it be reasonably to make the following changes to the control cards :

Suggested changes to avoid a SURGE in REAL/VIRTUAL storage use :
 
- Remove CONCURRENT
- Change OPTIMIZE to OPTIMIZE(3)
 
Explanation for  :
 
a) CONCURRENT :
 
Attention: Performing concurrent copy operations against many large data 
sets when there is also heavy update activity (such as reorganizing data sets 
or initializing the volume the data sets reside on) can result in a shortage of 
storage. The shortage occurs because data is transferred to data-space 
storage faster than DFSMSdss can process it. 
 
b) OPTIMIZE specifies the number of tracks to be read at a time, as follows:

If n is 1, DFSMSdss reads one track at a time. 
If n is 2, DFSMSdss reads two tracks at a time. 
If n is 3, DFSMSdss reads five tracks at a time. 
If n is 4, DFSMSdss reads one cylinder at a time. 

If OPTIMIZE is not specified, OPTIMIZE (1) is the default. Specifying OPTIMIZE 
(2), (3), or (4) reduces the time for a dump. Notice that this keyword uses 
more real and virtual storage. It also keeps the channel busy for longer blocks 
of time.
                                  
Anton Britz

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to