allfusion endevor change manager uss/hfs jcl parameters
TRANSCRIPT
Allfusion Endevor Change Manager
USS/HFS JCL PARAMETERS
Agenda
DSNTYPE PATH PATHDISP PATHMODE PATHOPTS Where used in Endevor
DSNTYPE
LIBRARY (pdse) HFS (Hierarchical File System) PDS … PIPE (special UNIX type)
DSNTYPE LIBRARY
//PDSE01 DD DSNAME=DATA.SET,
// DISP=(NEW,CATLG,DELETE),
// DSNTYPE=LIBRARY,
// SPACE=etc..
DSNTYPE HFS
//NEWHFS DSNAME=OPENMVS.DSA,
// DISP=(NEW,KEEP),
// SPACE=(TRK,(10,10,1)),
// DSNTYPE=HFS
DSNTYPE PIPE
//PIPE01 DD DSNTYPE=PIPE,
// etc...
PATH
//PIPE01 DD DSNTYPE=PIPE,
// PATH=‘/finance/test/market/data’,
// etc...
PATHOPTS
FILE ACCESS
ORDONLY OWRONLY ORDWR
PATHOPTS
FILE STATUS
OAPPEND OCREAT OEXCL
PATHOPTS
//PIPE01 DD DSNTYPE=PIPE,
// PATH=‘/finance/test/market/data’,
// PATHOPTS=(OWRONLY,OEXCL,
// OCREAT), …..
PATHDISP
DISPOSITION
KEEP DELETE
PATHDISP
PATHDISP=(KEEP,KEEP)
PATHDISP=KEEP (keep,keep)
PATHDISP=DELETE (delete,delete)
PATHDISP=(,DELETE) (keep,delete)
PATHMODE
SIRUSR SIWUSR SIXUSR SIRWXU SIRGRP SIWGRP SIXGRP SIRWXG SIROTH etc….
PATHMODE
//PATHEXMP DD PATH=‘/finance/test/market.data’,
// PATHOPTS=ORDONLY,
// PATHDISP=(KEEP,DELETE),
// PATHMODE=(SIRWXU,SIRGRP)
Endevor’s use of USS
Potential uses :
As a base file As a source output library NOT as delta file …. Why Would We ? In your processors, of course
Questions
?
Allfusion Endevor Change Manager
ELEMENT CATALOG DESCRIPTION
CATALOG
Indexed by (long) element name and type
Alternate index on element name in MCF Location segments Selection data
CATALOG
One catalog per C1DEFLTS table Built once only: 400K elements in 10
minutes (was 22 hours on 1st beta version)
Updated when MCFs are updated Excellent RLS/LSERV candidate
CATALOG
Optimized Searches Only element name use catalog lookup Only SYS/SBS with wild element name
use MCF info Avoid wildcards on 1st byte where
possible THE MORE YOU QUALIFY, THE
FASTER THE QUERY.
Allfusion Endevor Change Manager
Nice New Features
Use them
Features to investigate
ESORT (3.9) EONLY and EPRINT (4.0)
EMAIL notification for approvers (3.9) EMAIL notification for SIGNOUT OVERRIDE
(4.0) EMAIL notification available to you using exits
Features to investigate
Element registration (avoid overlays) ELEMENT NAME uniqueness NAME/OUTPUT-TYPE uniqueness Can be activated in
WARN/CAUTION/ERROR mode
Features to investigate
SITE VARIABLES in .SOURCE(member) pointed to by parameter in C1DEFLTS
PATH statement(s) used for type definitions COBOL LIBRARY NAME (no more overrides) Anything you want (but static) We intend to allow you to add variables
dynamically
Allfusion Endevor Change Manager
ACMQ 4.0 build
for new ACMQ users
ACMQ build
Mandatory step to populate ROOT/XREF files, this can take a few hours !
Determine BASE/DELTA library type and optimize for conversion.
Test conversion using release 3.9 cloned data to see what performs best
Swap (temporarily if necessary) to best performing dataset type and build ACMQ data
Use permanent files, better if x37 occurs Convert back to old type if desired