| |
 |
|

|
Functional
Overview
|
 |
SmartJCL
validates the syntax of all JCL statements. This
rules out frequent causes of errors such as missing
continuation characters and incorrect parameters.
|
 |
SmartJCL
can be called by an edit macro directly from the
ISPF editor. |
 |
SmartJCL
can be called as a batch program: Complete production
sequences can be checked in advance. Jobs can be
selected using lists or OPC fields such as application
ID, owner or workstation. |
 |
SmartJCL
SmartJCL has interfaces to Control-M and TWS. |
 |
SmartJCL
allows validation of site specific standards by
using the REXX interface. |
 |
SmartJCL
checks disposition parameters and corresponding
file allocations for logical mistakes. If a job
tries to read a file with DISP=SHR and the file
does not exist, SmartJCL returns an error. |
 |
SmartJCL
validates GDG processing. |
 |
SmartJCL
checks the availability of programs and procedures. |
 |
SmartJCL
can read JCL directly from Librarian libraries. |
| |
|
| |
|
 |
ISPF
Edit Macro |
| SmartJCL
can be called from the ISPF editor. Error messages
are displayed as NOTE lines. Labels enable users
to locate "incorrect" statements using
the L(ocate) command. Advantages are: |
 |
Jobs
can be checked and corrected during editing. |
 |
Messages
are displayed in the editor right at the place where
the error was found. |
 |
A
summary of all errors at the beginning of the job
makes it possible to jump to them directly using
the locatecommand.
Handling is simple. |
 |
The
user does not need any special knowledge, training
or manuals. |
| |
 |
| |
|
 |
Scheduler
Interfaces |
| One
of the main advantages of SmartJCL is the integrated
scheduler interface for IBM's TWS (OPC) and BMC's
Variables are substituted by the corresponding values,
JCL can be correctly validated. |
| |
|
| |
|
| |
|
 |
REXX
Interface |
| SmartJCL
has an integrated REXX interface. It allows to adapt
SmartJCL flexible and easily to customer specific
needs, from simple verification of company standards
up to complex handover systems. The interface is
designed as a REXX "function package". |
 |
All
JCL statements can be accessed for verification
and modification |
 |
The
Function Package contains special functions for
JCL handling, e.g. Qualifier("USER.PROD.TYPE",
LAST)="TYPE¡° |
 |
The
Function Package contains SET functions to delete,
insert or modify all statements, even complete steps
|
The
example below shows how to scan the JOBLIB, and
delete all DSNs from the JOBLIB, which are already
present in the
LINKLIST: |
| |
|
| |
The
interface can be used in batch mode to check and
modify complete libraries.
|
| |
|
| |
|
| |
|