I use the DISKWRIT program to tell if a CMS R/O minidisk has been altered
 
and it needs to be re-accessed.  You can find the source code for 
DISKWRIT, (and a PIPELINE REXX routine to check and re-access multiple 

minidisks), at the following location:

http://listserv.uark.edu/scripts/wa.exe?A2=ind9902&L=IBMVM&P=
R4298&I=-
3&X=28F5D223A5016EB90D&Y=dale-smith%40columbus.rr.com

or:  http://tinyurl.com/yh4kfhp

-- 
Dale R. Smith

"In all large corporations, there is a pervasive fear that someone,
somewhere is having fun with a computer on company time.      
     
Networks help alleviate that fear."             
                   
- John C. Dvorak                   
                         
       

On Tue, 9 Mar 2010 09:55:59 -0500, Horlick, Michael 
<[email protected]> wrote:

>Greetings,
>
> 
>
>I would like to know if there is a CMS command/program out there that ca
n 
quickly determine if a CMS disk has been changed?
>
> 
>
>The reason: We run the ASG ZEKE product that runs in our z/VSE machines 

that communicate via a SMSG to a CMS machine that actually sends the JCL 

to the reader of the requestor. The JCL could be on several CMS disks so 
I 
have added CMS ACCESSes each time a SMSG comes in. Here is the console 

from a ZEKE CMS machine:
>
> 
>
>DMSCYW2245I *SMSG MUHC24 00236 EPIBCATZ BKUP EPIBCATZ 03   0 NONE NONE *
 
Z       
>
>TIME IS 07:04:15 EST MONDAY 2010-03-
08                        
                   
>
>CONNECT= 99:59:59 VIRTCPU= 000:14.36 TOTCPU= 
000:21.53                      
     
>
>DMSACC724I 193 replaces B 
(193)                       
                         
  
>
>DMSACP723I B (193) 
R/O                        
                         
          
>
>DMSACC724I 194 replaces C 
(194)                       
                         
  
>
>DMSACP723I C (194) 
R/O                        
                         
          
>
>DMSACC724I 195 replaces E 
(195)                       
                         
  
>
>DMSACP723I E (195) 
R/O                        
                         
          
>
>DMSACC724I 196 replaces F 
(196)                       
                         
  
>
>DMSACP723I F (196) 
R/O                        
                         
          
>
>JOB INFO FROM MUHC24 WAS EVENT 00236 FNAME EPIBCATZ FTYPE 
BKUP                   
>
>-------- -------- ----- JOB EPIBCATZ PRI 03 SYSID   CLASS 
0                      
>
>-------- -------- ----- USERINFO NONE NONE SUBMIT Z TARGET 
MUHC24                
>
>PUN FILE 7783 SENT TO   MUHC24   RDR AS  9406 RECS 0012 CPY  001 Q NOHOL
D 
NOKEEP 
>
>ZEK11E000I PROCESSING COMPLETE. OUTPUT 
RECORDS=12                     
           
>
> 
>
>Those ACCESSes , probably 98% of the time, don't have to be done (since 

the JCL doesn't change that often) but we issue them just in case a disk 

or disks change. 
>
> 
>
>We have a problem when ZEKE requests from VSE machines start coming in 

quickly and the CMS machine(s) just can't keep up with them. ZEKE 
complains with a message on the z/VSE console:
>
> 
>
>Z2 0074 Z0641E Event 000078 ver 00000 dispatch attempted-CMS machine not
 
receiving                      
                         
           
>
> 
>
>I know I can go SFS for those disks but we don't have it set up and to d
o 
it for this problem I'm not too keen on it (probably because I'm old and 

lazy and the need to educate the schedulers is too much trouble).  
>
> 
>
>So, I'm looking for a (super)quick resident CMS module that given a 
virtual disk address can tell if that CMS disk needs to be re-accessed.
>
> 
>
>Has it been written already and, if not, which manual(s) would have the 

info for me to write it?
>
> 
>
>Thank you,
>
> 
>
>Mike Horlick
>
>Conseiller
>
>CGI Gestion Intégrée des Technologies
>
>1350 Boul. René-Lévesque Ouest
>
>Montréal, Qc, H3G 1T4
>
> 
>
>

Reply via email to