Sign In

Dz Challenge: Tips and Techniques Got a great tip or technique to share?
z & A > Dz Challenge: Tips and Techniques > Vote now in the Destination z Tips and Techniques Challenge! View modes: 
User avatar
Advanced member
Advanced member
mwestholder - 5/8/2012 2:04:16 PM
   
Vote now in the Destination z Tips and Techniques Challenge!
Select from our three finalists:

1. Figuring the age of a Temporary Storage Queue
When you use Temporary Storage Queues to share data between CICS transactions, it is often necessary to run a periodic "clean up" transaction, which will delete obsolete TS Queues - these are Queues that have not been used for some time.

In these cases, you can use the INQUIRE TSQUEUE with the LASTUSEDINT option. This will return the interval in seconds since the TS Queue was last referenced.


2. A poor man's programmed operator
Most sites have automatic operator software implemented. During a z/OS upgrade however, you do not want them to intervene until you have successfully run the Imp’s of the BCP. Typically, you install the base z/OS, including exits, WLM settings and usermod's, import the old master as user catalog, check PARMLIB settings, etc. before you want to invoke the automatic operator on a flash copy. There’s a lot of work to be done, before even attempting to turn on the green lights for customer testing. Your mileage may vary but in my experience it takes a lot of IPL's before you reach that level. Meanwhile you are the sole operator to do the shutdown/IPL sequence. Two things might help. One is to put some automatic replies into in the (z/OS V1R12) AUTORxx PARMLIB member, the second one is to launch a job that does a shutdown of most of the system. I include an example (used while upgrading to z/OS V1R12) below. The first job (JES2 command before JOB card) ensures that JES2 will honor the commands submitted in jobclass (A) between the JOB and the EXEC card. The second job contains a numbers of commands you would have to enter during a normal shutdown without automatic operator. The last command in the example is site specific. What I do is to get out of EDIT sessions, and submit the job. Mind that it does not do all the work, JES2 for instance you have to stop manually.

Example:
/*$TJOBCLASS(A),COMMAND=EXECUTE
//JEDSP001 JOB OS-SETUP,'JED:SP JAN@JEDSP.NET',CLASS=A,
// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID,
// REGION=0M
//*
//S0 EXEC PGM=IEFBR14
//*
//JEDSP001 JOB OS-SETUP,'JED:SP JAN@JEDSP.NET',CLASS=A,
// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID,
// REGION=0M
// W
// RACF STOP
// F DLF,MODE=DRAIN
// P TNF
// F RMF,NODDR
// P GMPSERVE
// F VMCF,REMOVE
// P TSO
// F HZSPROC,STOP
// F BPXOINIT,SHUTDOWN=FORKINIT
// P OMVS,STOPPFS=ZFS
// P FTPD1
// P FFST
// P HZSPROC
// P LLA
// P VLF
// % STOP
// P SDSF
// P TCPIP
// P RMF
// Z NET,QUICK
// P DLF
// $PJES2,TERM
// V XCF,MVSZ,OFF (reply SYSNAME=MVSZ) <-------Site specific
//S1 EXEC PGM=IEFBR14


3. COMPARE SESSION Command
Consider that you are editing a file/program and you want to know the changes you have done since the last SAVE command. How to find that?

Give "COMPARE SESSION" or "COMP * X" on the command line.

User avatar
Member
Member
Anoop Thomas - 5/10/2012 3:03:49 AM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
the 3rd one is a tip which can be used in our everyday work.

User avatar
Member
Member
jjgmail - 5/11/2012 5:19:42 AM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
Tip number 2 is not just about shutting down a system. It demonstrates how to issue JES2 and system commands from a batch job. I use it in a sequence:
JOB1
- assembly
- link loadmodule into LLA library
- submit JOB2 through internal reader

JOB2
JOB CARD
system command: // F LLA,UPDATE=YL
EXEC CARD

User avatar
Member
Member
bpljzz - 5/17/2012 6:43:01 AM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
Tip 2 can be used for other things as well, besides shutting down a system, the others are well documented commands.

User avatar
Member
Member
ckreiter - 5/10/2012 8:46:21 AM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
All three tips are excellent. However, tip #3 is one I would use most often.

User avatar
Member
Member
Pimenta - 5/10/2012 11:21:06 PM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
The tip number three is to have the most practical content in day-to-day mainframe professionals. Simple, objective and efficient. Very good hint! We need this type of procedure to almost all the time.

User avatar
Member
Member
marc_yves2001@yahoo.fr - 5/11/2012 6:18:23 AM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
Sincerely, in my case, the COMPARE SESSION Command is the best. Great tip!

User avatar
Member
Member
viburnumx - 5/11/2012 3:31:46 PM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
Tip 2 is great. Not in a manual like the other two's. Generalized it gives you an enormous power over the machine. Just like inn the old days.


Viburnumx

User avatar
Member
Member
Piri - 5/16/2012 6:50:15 AM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
I prefer tip number 2 because we also have automatic operator software implemented.

User avatar
Member
Member
jinfocura - 5/17/2012 10:07:20 AM
   
RE:Vote now in the Destination z Tips and Techniques Challenge!
Tip 2 can be used to issue a batch of commands by starting an STC with the jobname as a parameter. The STC could ICEGENER the job including the command sequence to an internal reader.

1