SYSAFF looks for a match on JES2 system name only. Nothing else. If there's a match by name, a job will execute there. Otherwise the job will wait (forever) until a matching system joins the MAS.
SCHENV is much more complex. If you've been in the mainframe biz a while, think of SCHENV as an official incarnation of the venerable 'abstract resource' manager (aka Mellon mods). The resources are abstract in that they don’t represent any particular JES2 entity. They are entirely user defined. The bits in the 16-byte SCHENV carry whatever meaning the installation assigns. If the string in JCL is non-zero, WLM will hold a job until at least one system matches. Resources that may be mapped might include time of day, presence of required support software, or a particular Db2 subsystem. The possibilities are limitless. We created an SCHENV schema in early Y2K. It supports JECL keywords that users can code for a variety of reasons to format the SCHENV string. This is all done in JES2 exits. Unlike SYSAFF, JES2 proper knows nothing about the SCHENV resources being managed. WLM commands turn resource availability on or off. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Sent: Saturday, January 26, 2019 7:53 PM To: [email protected] Subject: (External):SYSAFF and SCHENV Hi It is just general question I was going through the manual. Does SCHENV perform the same function as SYSAFF ? Or it does more than that ? Peter ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
