Abstract for JES2 Initialization and Tuning Guide · How to send your comments to IBM · Summary How to initialize JES2 in a multi-access SPOOL configuration. JES2 Initialization and Tuning Guide. z/OS JES2 Initialization and Tuning Guide contains the following information in support of JES2 Email Delivery Services. JES2 initialization statement and parameter summary tables · JES2 initialization statement descriptions · APPL(jxxxxxxx) – Application Characteristics.

Author: Kak Groshicage
Country: Antigua & Barbuda
Language: English (Spanish)
Genre: Life
Published (Last): 20 December 2016
Pages: 46
PDF File Size: 2.16 Mb
ePub File Size: 10.67 Mb
ISBN: 332-8-66603-573-8
Downloads: 49597
Price: Free* [*Free Regsitration Required]
Uploader: Moogule

In dual initia,ization, the down-level data set is the data set which was not read from. Preliminary to that, we might want to know a little about the basic pieces involved.

IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

JES2 acquires, uses, and frees the checkpoint inktialization a time slice basis which is set by the installation. TSO submit, cancel, and status commands are slow.

CHANGES “z/OS V1R JES2 Initialization and Tuning Guide” IBM Library Server

This information references the following publications for further details about specific topics. You can then analyze the trace information that is in the dump.

Each such system has a copy of JES2 running. It discusses the key components of the JES2 infrastructure in the context of performance goals.


JES2 Initialization and Tuning Guide

However, by looking at external processes, you can make judgements regarding JES2 performance and its ability to get to the checkpoint data set. This gives availability benefits. Spool affinity is not controlled by a JES2 initialization statement. Where to find more information This information references the following publications for further details about specific topics.

Chapter Security considerations – JES3 to JES2 Migration Considerations [Book]

The idea for this post came from a suggestion by Ian Watson. The affinity is system based, not job based. There are no hard and fast recommendations to follow. In reality, the HOLD parameter is a minimum hold value. Frequently, run system jobs can be isolated on separate volumes leaving the remaining volumes to be exploited by user-defined work. This round-robin approach might break when the number of JES2 members increase. Just because one member is unable to access the queues another member might be performing useful work.

However, it does provide useful information that you can use in performance analysis. You can change the value dynamically using an operator command or the online SDSF interface. A useful command to help diagnose this is the following: This is often when the owning JES2 address space is not running due to a failure or having not been partitioned out of the sysplex. The primary write operation is used to bring the down level DASD copy of the queues up to date. This information also includes a summary table of the JES2 initialization statements and their primary parameters.


If the HOLD parameter is set lower than the time it takes for the primary write to 2 JES2 Performance and Availability Considerations complete, the hold time is extended until the primary write completes. However, connectivity speed is not the main benefit. Because spool volumes are read by a number of vendor products including SDSFany change to how spool addressing operates affects these products.

The LOCKOUT parameter reflects the time between a member being denied access to the shared queues and the time the controlling member is assumed to be down. The meanings of the individual job classes are totally made up for each site. At this point, the suggested way is initializarion switch more to a contention mode approach.

Many sysout files are never really printed, but are viewed and further processed directly from the spool space under TSO using a software product like SDSF. Automation routines should react to these messages and purge non-critical output on a regular basis to ensure that limits are not breached. JES2 uses more processor cycles.

Related Posts