• • Abstract for JES2 Initialization and Tuning Guide
  • z/OS Version 2 Release 1 summary of changes
• JES2 initialization
  • Installation overview
  • Service considerations
  • JES2 initialization process overview
    • Modifying how JES2 performs initialization
  • JES2 sample initialization data sets
  • Initialization statements and parameters
  • Using compaction on SNA workstations
    • How compaction works
  • Defining JES2 to the cross-system coupling facility (XCF)
    • How JES2 determines the JES2 XCF group name
    • XCF group name restrictions
    • How JES2 determines the JES2 XCF group member name
  • Defining JES2 structures in a CFRM policy
  • How to control JES2 initialization
    • Creating an initialization data set
      • JES2 initialization statements
      • Specifying JES2 command and message prefixes
      • JES2 initialization control statements
      • The JES2 patching facility
      • JES2 and MVS operator commands within the JES2 initialization data set
    • Sample JES2 initialization data set and HASPLIST corrections
    • Creating the JES2 cataloged procedure
      • Specifying a back-up JES2 cataloged procedure
    • Specifying user PROCLIBs
    • Using dynamic PROCLIB allocation
      • Using the PROCLIB(xxxxxxxx) initialization statement
      • Displaying the PROCLIB(xxxxxxxx) initialization statement
      • Modifying the PROCLIB(xxxxxxxx) initialization statement
    • Defining the data set for JES2 initialization parameters
    • Specifying the Start Options
      • Starting Using a JCL Procedure
      • Starting Using the Console
      • JES2 start options
    • Controlling initialization using JES2 exits and the $SCAN facility
  • Controlling JES2 load modules
    • JES2 load modules
    • Loading JES2 subsystem support modules
    • JES2 subsystem module placement and storage considerations
  • Controlling the loading of installation-defined load modules
  • Starting and stopping JES2
    • JES2 program properties
    • Starting JES2 for the first time (a cold start)
      • JES2 console messages during initialization
    • Performing an orderly shutdown of a JES2 member
      • Running with disabled JES2 processors
    • SMF record summary: starting and stopping JES2
    • Using event notification signalling with JES2
  • Restarting JES2
    • Cold start
    • Warm starts
      • All-member warm start
      • Single-member warm start
      • Quick start
      • Hot start
      • $E MEM command start
      • Warm start considerations
        • Warm Starting with multiple JES2 levels in a MAS
          • Verifying Checkpoint Time Stamps
        • Rebuilding JES2 job queues
        • Validation of JES2 track group map
        • Restarting JES2 with missing SPOOL volumes
      • Hot start considerations
        • Initialization statements
        • Exit facility
        • Functional subsystem reconnection
    • Restarting JES2 after an orderly shutdown
    • Restarting JES2 after a system failure
    • Specifying job journaling to ease restart processing
  • Modifying JES2 initialization statement specifications
  • How to correct initialization errors
  • Poly-JES
    • Defining a secondary JES2 member to MVS
      • Installing a JES2 secondary subsystem
        • Enabling the AUTOEMEM option on a secondary subsystem
    • Starting an alternate JES2 subsystem as a primary subsystem
  • How to initialize JES2 in a multi-access SPOOL configuration
    • Accessing JES2 SPOOL information in a MAS
    • Accessing JES2 checkpoint data sets in a MAS
    • Initializing the multi-access spool configuration
    • Starting the multi-access SPOOL configuration
    • Job submission and queuing
      • Displaying or updating a job's affinity
      • Scheduling environment
      • Using RACF multi-level security
      • Restarting jobs
      • Duplicate job names
      • Priority aging
    • Output
    • RJE
    • TSO/E
  • Functional subsystem support
    • Functional subsystem and functional subsystem interface
    • Using functional subsystems in a poly-JES environment
    • Functional subsystem recovery procedures
• Controlling JES2 processes
  • Devices
    • Defining device configuration
    • Assigning devices dynamically after initialization
    • Remote line and device configuration
      • Network job entry (NJE)
      • Remote job entry (RJE)
    • Directing responses to display commands
  • Job submission
    • Card readers
    • Network jobs
      • Processing JES2 control statements
      • Network job transmitter
      • Network job receiver
        • Identifying jobs received from the network
      • Controlling network job headers and trailer areas
      • Controlling network job transmitters and receivers
        • Job transmitter selection
  • Conversion
    • JCL conversion
    • Scanning the JOB statement accounting field
      • JOB statement accounting field scan exit
    • Network accounting
    • Converter parameters
    • Defining a job's procedure library
  • Job selection and execution
    • The JES2 job queue
    • Job class
      • Job class characteristics
      • Job class groups
      • WLM classification
      • Modifying jobs and classes
    • Job scheduling priority
      • Specifying priority
      • Calculating priority
    • Member affinity
    • Job scheduling environment
      • Displaying and controlling scheduling environments
        • SDSF options
        • SMF recording
    • Duplicate job name control
    • Held jobs
    • Setting job class limits for execution
    • Enabling job execution selection
    • Controlling job execution through exits
    • Controlling the sequence of job execution
      • Serial job execution sequence
      • Concurrent job execution sequence
    • JES2 control of batch job initiation
      • Operator control of the batch job workload
      • Using job classes with JES2–managed initiators
      • JES2 initiator attributes
        • Naming initiators
      • Job priority aging
    • WLM control of batch job initiation
      • Controlling batch job selection
      • SMF recording
        • SMF type 26 records
        • SMF type 30 records
        • SMF type 72 records
      • Considerations for WLM goals applied to batch jobs
        • Alignment of initiator mode and service classes
        • Queue delay measurements
        • Multiple JES2 MAS complexes in a sysplex
        • WLM poly-JES considerations
    • The initiator cataloged procedure
    • System resource manager control of the batch job workload
    • Job monitoring
      • Monitoring the successful completion of a job
    • Entering commands from a job stream
    • Execution batch monitoring (XBM) facility
      • Using the execution batch monitoring facility
  • Output
    • Default data set characteristics
    • Output priority
    • Output priority aging
    • Output processing
      • Output data set groups
      • SMF record summary: job-output related information
      • Routing output to other nodes
        • NJE transmission selection
    • Considerations for output produced by APPC transaction programs
      • System data sets
    • Output class assignment
      • Characteristics of output classes
      • Blank truncation
    • Setup characteristics
    • Demand setup and output data set grouping
    • Spin data set processing
    • Spin data sets in the NJE environment
    • System data set characteristics
    • Specifying JES2 output size limits
    • Variable work selection criteria
      • Specifying work selection criteria
      • Determining the “best” JOE
      • Tuning work selection criteria
    • Output disposition for SYSOUT data sets
      • Specifying output disposition
      • Overriding output disposition
        • Changing output disposition through JCL
        • Changing output disposition through TSO/E
        • Changing output disposition through operator commands
      • Purging JES2 system data sets
      • Offloading and reloading SYSOUT based on output disposition
        • Changing output disposition during reload
      • Transmitting output to another node
      • Automatic restart management
    • Dividing output into smaller units
    • Defining output limits
      • Considerations for started tasks and TSO LOGONs
    • SAPI POST and GET SYSOUT work selection optimization
    • Enabling and disabling SAPI POST and GET SYSOUT-Index optimization
  • JES2-provided client print services
  • Printers and punches
    • Print chain alias for 1403 and 3211 printers
    • 3211 indexing
    • Defining the advanced function printer (using the PRT(nnnn) statement)
    • Defining a functional subsystem for advanced function Printing (using the FSS(accccccc) statement)
    • Using advanced function printing printers
      • Compatibility-mode support
      • Full-function mode support
    • Creating output for a 3540 diskette writer
    • The JES2 print separator
      • Modifying the JES2 print separator
    • Creating a JESNEWS data set
    • JES2 system data sets
      • The JES2 job statistics
    • The JES2 punch separator card
    • Output routing
      • Routing data sets
      • Pooling remote devices
      • Specifying default output routing on input devices
        • Allowing output devices to select route codes
      • Using destination identifiers to route output
        • Specifying SYSOUT destination through JES2 route codes
          • Routing Output After a Configuration Change
        • Specifying SYSOUT destination through user routing
    • How JES2 resolves destinations from node to node
      • Origin-node processing
        • Case 1
        • Case 2
      • Destination-node processing
        • Examples of JES2 routing SYSOUT destinations
          • Example 1
          • Example 2
          • Example 3
          • Example 4
          • Example 5
      • Routing output to devices at another node
      • Avoiding endless looping in a network
      • Specifying TSO/E userIDs on a JES2 system
    • Altering destination processing through DESTDEF
      • Preparing installations to alter destination processing
      • Routing to multiple destids
      • Routing to RJE devices when Rdest=User
        • Reducing printing costs through remote pooling
    • External writers
    • Held job and data set considerations
      • Defining held data sets
      • Held output processing
      • Modifying and disposing held data sets
      • Offloading held jobs and data sets
      • Held data sets in the NJE environment
  • Improving JES2 processing
• SPOOL volume configuration, control, and performance
  • SPOOL configuration
    • The SYS1.HASPACE data set
      • Naming conventions
      • Placement
      • Space allocation
  • Defining SPOOL space
    • SPOOL allocation
    • Controlling SPOOL space
    • Defining the allocation IOT
    • Defining the track group maps
    • SPOOL partitioning
      • Using the FENCE parameter to partition SPOOL volumes
        • Associating SPOOL volumes with MAS members
        • Refining spool volume selection
      • Allocating tracks and track cells
      • Handling defective track groups
    • Dynamic addition and deletion of SPOOL volumes
      • Status of SPOOL volumes
      • Addition of SPOOL volumes
      • Deletion of SPOOL volumes
      • Performance considerations and recommendations
    • Copying a SPOOL volume
    • Recovering from SPOOL volume failure
      • Replacing a damaged spool volume
  • SPOOL performance considerations
    • Selecting SPOOL devices
    • Allocation of SPOOL space
    • Track celling
  • SPOOL offload facility
    • Overview
    • Defining the offload facility
      • Selecting jobs and SYSOUT through work selection
      • Using uncataloged data sets
      • Using pre-cataloged data sets
    • SMF record summary: transmitting and receiving jobs and SYSOUT
    • Offloading all pre-execution jobs and SYSOUT
      • Job disposition
    • Reloading all pre-execution jobs and SYSOUT
    • Offloading selected jobs and SYSOUT
    • Reloading selected jobs and SYSOUT
    • Using the SPOOL offload facility for networking
• Checkpoint data set definition and configuration
  • JES2 checkpoint function
    • Placement of the checkpoint data set
      • Primary checkpoint on a coupling facility structure; secondary checkpoint on DASD
      • Both checkpoints on DASD
      • Benefits of using a coupling facility
  • Checkpoint data set specifications
    • CKPTn data set definition and placement on a coupling facility
      • Recommendation for initializing a checkpoint on a coupling facility structure
      • Ensuring the integrity of checkpoint data
        • Ignoring the volatile status
        • Requesting operator intervention for volatile status
        • Requesting immediate invocation of dialog
    • CKPTn data set definition and placement on DASD
      • Controlling the size of the change log
      • Storage management considerations on DASD
  • Determining the size of your checkpoint data set
    • Determining the current checkpoint size
    • Determining the new checkpoint size
    • Calculating the checkpoint size
      • Specifying the storage of checkpoints on DASD
      • Syntax for checkpoint space allocation on DASD
      • Specifying the storage of checkpoints on coupling facility structures
      • Approximate storage requirements on coupling facility structures
      • Detailed storage requirements on coupling facility structures
  • Placing a checkpoint on a coupling facility for the first time
    • Correcting a structure error of size
    • Correcting a structure error of incorrect attributes
  • The checkpoint cycle
    • Checkpoint cycle overview
    • Phase I - Checkpoint RESERVE, lock, and read
    • Phase II - Updating the checkpoint
    • Phase III - Final checkpoint write and data set release
    • Phase IV - Other member access
  • Checkpoint configuration modes
    • DUPLEX-mode processing (with backup)
      • DUPLEX (with backup) on DASD
      • DUPLEX (with backup) on Coupling facility
    • DUPLEX-mode processing (without backup)
      • DUPLEX (without backup) on DASD
      • DUPLEX (without backup) on Coupling facility
      • Effects of error situations when DUPLEX=OFF
    • DUAL-mode processing
      • Example of DUAL mode in a 2-member MAS configuration
      • Example of DUAL mode in a 3-member MAS configuration
  • Accessing the CKPTn data set in a MAS
    • Controlled checkpoint data set access
      • HOLD= parameter on the MASDEF statement
      • DORMANCY=(mmmm,nnnn) parameter on the MASDEF statement
        • DORMANCY(mmmm) specification
        • DORMANCY(,nnnn) specification
    • Member-specific parameter recommendations
    • Contention-driven checkpoint data set access
  • Replacement data set (NEWCKPTn) definition
    • Space allocation for NEWCKPTn data sets
      • Specify the NEWCKPTn data set during initialization
      • Specify the NEWCKPTn data set through the $T CKPTDEF command
      • Specify the NEWCKPTn data set during reconfiguration ($HASP271)
      • Specify the NEWCKPTn data set during reconfiguration ($HASP282)
    • Placement of the NEWCKPTn data sets
    • Using the NEWCKPTn data sets
  • Checkpoint reconfiguration: An overview
    • Checkpoint reconfiguration concepts
    • Preparing for checkpoint reconfiguration
      • JES2-initiated because of I/O error
      • Predefining replacement checkpoint data sets
    • Using the checkpoint reconfiguration dialog
      • Message routing during a checkpoint reconfiguration
      • Determining the reason for a checkpoint reconfiguration
      • Dialog options: CANCEL and TERM
    • JES2-initiated entrance into the dialog
      • Initialization
        • Example reconfiguration dialog at initialization
      • I/O error
        • Minimizing operator involvement
        • Requesting operator involvement
        • Example reconfiguration dialog for I/O error
        • Operator intervention when errors occur during a reconfiguration
      • Volatile coupling facility
        • Example reconfiguration dialog for volatile coupling facility
    • Operator-initiated entrance into a checkpoint reconfiguration dialog
      • Moving a checkpoint data set
      • Replacing a checkpoint data set
      • Discontinue using a checkpoint data set
      • Example operator-initiated reconfiguration dialog
    • Checkpoint reconfiguration recovery
      • Driving member failure
      • Recovery from JES2 member failures
      • Initiating member(s) failure in start-up processing
      • Member delayed
    • Clean-up after a checkpoint reconfiguration
      • Returning to your typical checkpoint data set definitions
      • Restarting JES2 from an emergency checkpoint
      • Making the checkpoint reconfiguration definitions permanent
    • Moving a JES2 checkpoint to a coupling facility using system-managed rebuild
  • Recovering from member failures on other JES2 members
    • Checkpoint on DASD
    • Checkpoint on Coupling facility structure
    • Using operator commands
      • JES2 failure only
      • MVS and JES2 failure
    • Using the AUTOEMEM option
    • Enabling the JES2 AUTOEMEM option at initialization
  • Providing copies of the JES2 checkpoint to application programs
    • Using Versions= to provide copies of the checkpoint data set for use by applications
• Network job entry (NJE)
  • Overview of NJE
    • Differences between Networking Protocols
    • Initialization statements
      • Logical and physical configurations
    • Hardware considerations for NJE
    • Data flow through a network
      • How the network processes jobs, commands, and messages
    • How JES2 processes jobs from TSO/E user IDs in NJE
      • How the network determines the execution node
      • How the network transmits input jobs and SYSOUT
      • Assignment of JES2 job identifiers
      • Determining the destination of output
  • Designing the network
    • General considerations
      • Network topology
      • Performance
      • Security
      • Node names
      • Resistance
        • Accounting
        • Cost
    • Network topology
      • Simple configurations
        • Simple 2-node
        • 2-Node with 2 parallel links
        • 4-node ring
        • 4-node ring with full connectivity
        • 5-node star
      • Complex configurations
        • Subnets with gateways
        • Backbone network configuration
    • Performance considerations
      • Compression
      • Compaction
    • Security considerations
      • Password processing
        • NJE secure signon
      • Encryption
  • Initializing the network job entry functions
    • Initialization statements
    • Naming the nodes in a network
      • Default names
      • Naming restrictions
      • Symbolic node names
      • Defining nodes using generics
      • Specifying multiple passwords for NJE connections
      • Using secure signon protocol for NJE signon
      • Dynamic changes of network information
    • Using destination identifiers (DESTIDs)
    • Defining a minimum configuration for BSC NJE
      • NODENUM
      • LINENUM
      • OWNNODE
    • Default NJE parameters (BSC, SNA, and TCP/IP)
      • Sending and receiving jobs and SYSOUT
        • Specifying transmitters and receivers
        • Specifying work selection values for NJE transmitters
        • Considerations when specifying NJE transmitters and receivers
      • Controlling jobs looping in the network
      • Routing output
      • Command authority
      • Network time tolerance
    • Using different operating systems in a network
      • Execution node considerations
        • User access authority (RACF)
        • Job account numbers
        • Job accounting information
        • Procedure libraries
        • Unit names
      • Output node considerations
        • Held Output
        • Lines per page
        • FORMDEF and PAGEDEF
        • JESNEWS
        • SYSOUT Classes
    • Defining a minimum configuration for SNA NJE
    • Special considerations for SNA NJE networking
      • Multiple parallel SNA NJE sessions between two nodes
    • VTAM definitions for SNA NJE
      • VTAM APPL statement
      • NJE bind image
      • SNA buffer size
        • Valid RU sizes
      • Specifying unique log-mode table entries for specific SNA connections
    • Defining a minimum configuration for TCP/IP
      • Setting up the JES2 initialization deck
        • NETSRV(nnn)
        • SOCKET(xxxxxxxx)
        • LINE(nnnn)
      • Commands
        • $S NETSRV(nnn)
        • $SLNE(nnnnn)
        • $SN,SOCKET=xxxxxxxx
        • JES2 commands
      • Example
    • Special considerations for TCP/IP NJE
      • Setting up TCP/IP
      • Defining a NETSRV
    • NETSRV security considerations
      • SSL and TLS
  • Displaying information about a network
    • Displaying NJE global parameters
    • Displaying node attributes
    • Displaying JES2 applications for SNA NJE
    • Displaying TCP/IP sockets
    • Display symbolic destination identifiers
    • Displaying active paths in a network
    • Displaying NJE connections
    • Sending a display command
  • Connecting the network
    • Starting BSC dynamic connections
    • Starting SNA dynamic connections
    • Starting TCP/IP dynamic connections
    • Using the network resource monitor
      • Starting and restarting networking devices automatically
      • Starting and restarting NJE connections automatically
      • Starting NJE connections manually
      • Using the JES2 network commands
    • SMF record summary: NJE (network job entry) processing
    • The path manager
      • Network connection control records
      • Non-path manager connections
        • Non-path manager protocol
        • Full path manager protocol within a network
    • Private connections
      • Summary of PATHMGR= and PRIVATE= parameters
    • Static connections
      • Using the CONNECT statement
      • Controlling static connections
      • Preventing looping when using connect statements
    • Defining and communicating between subnets
    • Determining path resistance
      • Calculating resistance for adjacent connections
      • Calculating resistance for non-adjacent nodes
      • Controlling store-and-forward transmissions
        • Using only direct connections to send data to another node
        • Using only direct connections to send data to a specific node
        • Preventing the use of a specific node as an intermediate node
    • Path selection considerations
      • PATH
      • RESTTOL
      • RESTMAX
    • Extending network capability
    • Adding a node to an existing network
  • Multi-access SPOOL configuration considerations for NJE
    • Example of a multi-access SPOOL node
    • Queuing messages to a multi-access SPOOL node
      • MASDEF queuing parameters
        • HOLD
        • DORMANCY (mmmm,nnnn)
      • NJEDEF queuing parameter
    • Defining a multi-access SPOOL node (SNA considerations)
    • Defining a multi-access SPOOL node (TCP/IP considerations)
      • Consistency of networking information across an MAS
• Remote job entry (RJE)
  • Defining RJE workstations to JES2
    • Planning for RJE workstation system growth
    • Defining RJE devices
    • Modifying RJE workstations
    • Recovering RJE workstations from failed members
  • SNA RJE considerations
    • VTAM LU and PU parameters that affect SNA RJE
    • VTAM APPL definitions for SNA RJE
    • SNA RJE buffer size
      • Valid RU sizes
  • BSC RJE processing
    • BSC multileaving workstations supported by JES2
    • BSC teleprocessing buffer considerations
  • SMF record summary: RJE processing
  • Defining lines for RJE workstations
    • Nondedicated lines
      • RJE BSC dial-up connections
    • Dedicated lines
  • Defining BSC lines for RJE workstations
  • Defining SNA lines for RJE workstations
    • RJE line passwords
    • Changing an RJE workstation from BSC to SNA
    • Changing an RJE workstation from SNA to BSC
  • Starting and stopping remote job entry
    • Options for disconnecting remote lines
    • BSC workstations
      • Format and definitions for the /*SIGNON statement
      • Format for the /*SIGNOFF statement
    • SNA RJE workstations
      • Initiating an automatic terminal connection
        • JES2 automatic logon capability
          • Making the RJE Workstation Eligible When Work Exists
          • Making the RJE Workstation Eligible Whether or Not Work Exists
        • Automatic logon considerations
      • Creating an SNA RJE connection
      • Using the VTAM LOGON command for SNA RJE
      • Using the VTAM LOGOFF command for SNA RJE
  • JES2 RJE bind image
    • Setting line density for RJE devices
  • Altering the sequence of operations from an RJE workstation
  • Pooling RJE workstations
    • Expanding RJE workstations
    • Consolidating RJE workstations
    • Using CONDEST= to specify the RJE operator console
  • Remote message spooling
• Providing security for JES2
  • MVS Security Authorization Facility (SAF)
  • Using RACF to provide security
    • JES2 access to resources
    • Securing resources
    • SMF record summary: RACF security
    • Defining and grouping your installation's support personnel
    • Specifying access authority
      • Universal access authority
      • Access lists
    • Security labels
    • Multilevel security support
    • Controlling access to data sets JES2 uses
    • Controlling input to your system
      • How RACF validates users
        • Propagation of security information
        • Propagating security information across a network
      • Controlling job submission
      • Controlling job modification and cancellation
      • Authorizing users to submit jobs for other users
      • Authorizing the use of input sources
      • Authorizing work from remote job entry (RJE) workstations
    • Authorizing networking jobs and SYSOUT (NJE)
      • Authorizing inbound work
      • Understanding networking profiles
      • Authorizing jobs
      • Authorizing SYSOUT
      • Validating SYSOUT based on the submitter
      • Understanding default userids
      • Translating security information
      • Authorizing inbound SYSOUT by translating the default userID
      • How JES2 propagates security information
      • Defining nodes as local SYSOUT sources
      • Authorizing outbound work
    • Controlling access to data that resides on SPOOL
      • Controlling access to SYSIN and SYSOUT
      • SPOOL browse access to SYSIN and SYSOUT
      • Protecting JESNEWS
      • Protecting trace data sets
      • Protecting SYSLOG
      • Protecting SPOOL offload data sets
        • Offload
        • Reload
    • Controlling where output can be processed
      • Controlling external writers
    • Authorizing the use of operator commands
      • Considerations for automatic commands
  • Using JES2 to provide security
    • JES2 initialization statements
    • JES2 security exit points
    • Multiple levels of a security product in a MAS
    • Controlling job class usage
• IBM devices supported by JES2 and how to use them
  • DASD utilization tables
• Miscellaneous JES2 facilities
  • Automatic command processing
    • Writing a day's work scheduler
    • Limiting considerations
  • Using the MVS message service (MMS) for JES2 messages
  • Managing storage in JES2
    • Storage considerations
      • JES2 private area virtual storage
      • Central storage
      • Storage isolation
    • Job journaling, SMF records and SMF exits
    • Spool utilization
  • The JES2 health monitor
    • Health monitor processing
    • Controlling the JES2 health monitor
      • Special command processing
      • $J (JES2 health monitor) commands
• The external writer
  • Overview of the IBM-Supplied External Writer
    • Characteristics of the IBM-Supplied External Writer
  • How to Set Up and Start the External Writer
    • The External Writer Cataloged Procedure
      • The EXEC Statement
      • The DD Statement
        • Special Printer Output Considerations
  • How the IBM-Supplied Output Writer Routine Works
    • Functions of the Output Writer Routine
  • How to Add Your Own Output Writing Routine
    • Replacing the IBM-Supplied Routine
    • Using Your Routine for Only Certain Jobs
      • Coding Conventions for the Output Writing Routine
      • Programming Considerations for the Output Writing Routine
      • How the IBM-Supplied Output Separator Routine Works
        • Separator Routine Parameter List
        • Output from the Separator Routine
        • How to Add Your Own Output Separator Routine
        • Using the Block Character Routine