This is a common problem ever since JES2 provided dynamic ($command) update for many parameters that used to require warm start, all-systems warm start, or even cold start. 'You would think' that IPL would do the trick as well as a command. For many parameters, it does not. That's why, when confounded by the inexplicable, $D may reveal the answer.
Be careful not slap your forehead too hard. ;-) . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Jorge Garcia <jgarc...@mapfre.com> To: IBM-MAIN@bama.ua.edu Date: 04/19/2012 08:46 AM Subject: Re: Jes job log unavailable in STC Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> Mark, It works fine. Thanks. We changed the OUTDISP parm in our JES2PARM last morning. We included OUTDISP=(HOLD,HOLD) from OUTDISP=(PURGE,HOLD). We ipled the system and we supposed that the parameter was active, but we were wrong. We've executed the $DJOBCLASS(STC),LONG command and it showed OUTDISP=(PURGE,HOLD), the old state. In JES2 tunning and reference specifies cold start o $T JOBCLASS for change the parameter. We've entered $T JOBCLASS(stc),outdisp=(hold,hold) and now we can view all STC sysout. It's an odd situation. We cannot change the parameter with a warm start and it works fine with a dynamic change. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
