|
The
Optional
JES2 Inspector:
The optional JES2 Inspector processes the
parameters used to define JES2 and determines JES2 operational
validity. During each Inspection the SYNTAX of each parameter is
CHECKED and the system resources needed for the successful
execution of JES2 are VALIDATED. The
JES2 Inspector is fully integrated into IMAGE Focus
allowing
users to quickly Test, Document, Compare and Monitor their JES2
Sub-System environment.
The Inspection involves syntax checking of all parameters and additional inspection processing that identify:
1. Syntax coding errors and
2. Definition errors in JES2 parameters.
Problems identified would generally prevent the next start of JES2. Users should correct identified problems as they may turn into JES2 initialization errors.
Stating an
Inspection
To start the JES2 Inspector, you must specify, "Yes" (Y) for JES2 Inspection in the PROCESSING OPTIONS section of the Image Inspection Definition Screen.
The JES2 Inspector fully supports the Report Level, Member Display and Store Package options in this section.
JES2 New Release Analysis
To start the JES2 Inspector for New Release Analysis, you must specify "Yes" (Y) for JES2 Inspection in the Processing Options section of the New Release Analysis Screen.
The Release Level value is set to "1" by default and would result in an analysis of the impact of attempting to run JES2 Images developed to support a prior release in an OS/390 V2R10 environment. Setting the Release Level to "2" performs the same analysis for z/OS V1R1. The JES2 Inspector fully supports the Report Level and Member Display options in this section.
Note: The JES2 Inspector may not support all of the latest release levels that are selectable. If an unsupported level is selected, the JES2 Inspector will perform the request but then issue a message stating that level is not supported. Full support for newer levels will be implemented as soon as access to the needed source information is available and can be analyzed.
Inspection
Process
If 'Yes" (Y) is specified for the JES2 Inspection processing option, IMAGE Focus will invoke the JES2 Inspector if:
1. The OPSYS Inspector finds a start command or sub-system definition for JES2 in the OPSYS parameters being processed.
2. And the OPSYS Inspector can locate the Started Task JCL for JES2.
3. And the OPSYS Inspector can determine the source of the JES2 parameters from that JCL and can successfully read those parameters.
Once invoked, the JES2 Inspector will first determine the level of the JES2 component on the system being inspected. The JES2 Inspector will then prepare to inspect the parameters using the rules for that release. If a New Release has been selected by using the IMAGE Focus New Release function, the rules (if supported) for the New Release are used in place of the rules determined by JES2 component level.
Syntax Inspection
The JES2 Inspector will check the syntax of all JES2 parameters and sub-parameters (over 890 different keywords in all). This is an independent analysis of the JES2 syntax based on JES2 documentation and known working syntax. No components of JES2 are used.
The JES2 Inspector parsing phase will detect invalid syntax format, invalid keywords, and invalid keyword values. Keyword values are checked to be valid fixed, numeric, numeric range, hexadecimal, or masked specifications.
Part of the Syntax checking phase includes checking for mutually exclusive keywords, restricted keywords (only valid when another keyword is specified with a particular value), and obsolete keywords.
Syntax Rules
The syntax rules, used by the JES2 Inspector, have been developed from a review of the IBM JES2 Initializing and Tuning Reference. These base rules and the testing of a large number of syntax variations using JES2 systems result in the Final Rule Set used by the JES2 Inspector. The JES2 Initialization and Tuning Reference is known to contain a number of inaccuracies. As these are discovered the Final Rule Set is updated.
Syntax Exceptions
Some JES2 statement syntax that was valid years ago and continues to work is not documented while other forms of syntax that are documented do not work at all. If the JES2 Inspector flags a statement as an error that in fact is being accepted by JES2, please contact NewEra customer support personnel at support@newera.com. Most likely the statement contains old undocumented syntax or is not documented properly.
As the JES2 Inspector is an independent analysis of the parameter statements, it can help to identify parameter specifications that are old and in an undocumented form. In these cases, it is advised to change these obsolete statements to a newer documented form. This way surprises can be avoided in the future if/when IBM removes support for older obsolete specifications.
The JES2 Inspector does not fully support the inspection of the rarely used selection limiting keywords. The JES2 Inspector will ignore any JES2 Commands specified within the JES2 parameter deck.
Post-Parsing Phase
The JES2 Inspector post-parsing phase will validate certain collections of parameters and the inter-relationship between them. Currently, the JES2 Inspector post-parsing phases are:
STC Definition Inspector
Allows IMAGE Focus to locate other system components that are started under the JES2 sub-system. IMAGE Focus must know which JES2 PROCLIB DD is used to locate started task JCL. The STC Definition Inspector will inspect the JES2 JOBCLASS PROCLIB= specification and provide the PROCLIB DD to IMAGE Focus.
Initiator Inspector
Inspects the JES2 INITDEF and INIT statements and the relationship between them. It will check that the number of defined initiators does not exceed the maximum and that all of the initiators are explicitly defined. It will also check initiator definitions that may be syntactically correct but may produce undesired results.
Network Inspector
Inspect the JES2 NJEDEF, NODE, CONNECT, and APPL statements and the relationship between them.
|
