* copyright (C) 1984-2019 merrill consultants dallas texas usa

in PDB.JOBS and PDB.NJEPURGE datasets with BUILDPDB.

Thanks to Scott Barry, SBBWorks Inc., USA.

Change 33.205 DB2ACCTP variables QPACPKID/QPACLOCN/QPACASCH/QPACAANM

VMACDB2 and QPACCOLN could be truncated even though they have

Sep 2, 2015 valid extended name segments. The LENGTH test for the

new PAR QUERY fields wrongly INPUT them when they did not

exist, causing the DELFIX circumvention to incorrectly be

invoked, causing the extended segments to not be input.

Thanks to Tom Adams, State Farm, USA.

Thanks to Shankar Chatterjee, State Farm, USA.

Change 33.204 Variable IOTMNODD was never calculated in PDB.JOBS/STEPS,

BUIL3005 and the value in IOTMTODD was actually IOTMNODD. The

BUILD005 three calculations of IOTMTODD= should be IOTMNODD=.

Sep 2, 2015

Thanks to Rick Southby, Insurance Australia Group Limited, AUSTRALIA.
Change 33.203 Cosmetic. EXCLUDED FIELDS FOUND messages now print your

VMAC110 site's IMACEXCL testing values, so you can see if this is

Sep 1, 2015 for a new dictionary triplet that needs a UTILEXCL rerun.

This was originally added in Change 29.262, but somehow,

the needed quotes and ampersand "&CICXLTR" syntax got

changed to CICXLTR, which printed nothing.

Change 33.202 Velocity ZVPS 5.4 dataset XAMSYT has zero observations

VMACXAM because Change 33.157's recalculated SYTNLPS was zero.

Aug 29, 2015 The actual SYTNLPS+1 in the non-Total record is now used

Sep 2, 2015 and the false INVALID SYTCUP SEGMENT message is removed.

Sep 11, 2015 -Unexpected CPID='GPs' value is now output in XAMCPUTO as

there were no records with CPID='Total".

Thanks to Douglas C. Walter, CitiCorp, USA.

Thanks to Brent Turner, Citigroup, USA.

Change 33.201 Support IBM INFOSPHERE CHANGE DATA CAPTURE VERSION 10.2.1

VMACCDC adds many new variables to the CDI, CDO, CDW, DLR, DSL,

Aug 30, 2015 DTC, OSC, SCT, SDT, TCT, and new TDT segments. However,

the SCT and TCT data does not match the documentation and

both SCTCPU and TCTCPU are invalid with this iteration.

Thanks to Phil Grasser, Norfolk Southern, USA.

Change 33.200 -TYPE70xx datasets have always contained ONLY data for the

VMAC7072 engines that were ONLINE at interval end, and that had

Aug 28, 2015 NOT been VARYed ONLINE (i.e., CAI='01'X). Engines that

were IPL's (CAI='03'X) were NOT output, because the data

in those startup intervals was inconsistent in early MVS.

However, those partial interval's data is not only valid,

it is actually now required to prevent wrong or missing

values for CECSER in TYPE70/TYPE70PR/TYPE70EN datasets,

and to capture the IPL interval's resources.

-TYPE70EN variable CPUBSYTM is now correctly set missing

for zIIP/zAAP engines, since it is a CP engine metric.

-More observations are now output, so PROC COMPARE will

see differences in these variables:

TYPE70: CECSER CPUACTTM CPUMVSTM CPUWAITM PCTCPUBY

PCTMVSBY PCTRDYWT PLCPRDYQ SHORTCPS

TYPE70PR: CECSER

TYPE70EN: CECSER CPUBSYTM CPUMVSBY
Change 33.199 The AXWAY SMF record was INCOMPATIBLY changed by an

VMACAXWY increase of a field length.

Aug 31, 2015

Thanks to Rachel Holt, FMR, USA.

Change 33.198 -CICS/TS 5.3 BETA, Resource Class (MNSEGCL=5) could cause

VMAC110 INPUT STATEMENT EXCEEDED INPUT because only 112 bytes of

Aug 27, 2015 the MNR5LENT=120 bytes were read.
Change 33.197 -Variable LPBUSY in TYPE113 is the TOTAL BUSY for all CPs

ASUM113 and can exceed 100% with multiple engines, but variable

VMAC113 LPARBUSY in ASUM113 is the CPU BUSY OF ONE ENGINE. New

Aug 24, 2015 variable LPBUSY is now created in ASUM113 with TOTAL BUSY

to provide both perspectives on percent busy.

-Variable SRBSTATE is now created in ASUM113 to complement

the existing PRBSTATE variable.

Thanks to David Cogar, Wells Fargo, USA.

Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.196 BVIR variable's values are revised to match IBM reports.

VMACBVIR TVCSIZE is now internally in bytes, formatted MGBYTES,

Aug 30, 2015 and the label corrected.

AVGCPUSE is now percent (95.5) instead of 0.95 fraction.

AVGDEFTH is now correct, was 1000 too large.

Thanks to Patricia J. Jones, DST Systems, USA.

====== Changes thru 33.195 were in MXG 33.08 dated Aug 20, 2015=========
Change 33.195 TMON/CICS Version 4.0 Support was still wrong, with an

VMACTMO2 extra 8 bytes INPUT that shouldn't have been, so that

Aug 20, 2015 MXG 33.08 dated Aug 20 is NOW required for version 4.0.

-Variables TASTCPUC and TASTCPOC in dataset MONITASK have

invalid data values, await PTF from ASG.

Thanks to Francois Vancoppenolle, PV Group, BELGIUM.

Thanks to Dirk Thys, PV Group, BELGIUM.
Change 33.194 -The modern CLRMFV Clist is incompatible with the archival

ZCLRMFV ZASMRMFV program because RMF III files are allocated with

Aug 19, 2015 RMFC prefixed DDNAMEs and the archival version of

ZASMRMFV is not aware of these. This results in message:

RMFV015E +++ERROR: NO VALID RMF III INPUT FILES FOUND+++

-A new Clist ZCLRMFV for use with ZASMRMFV only is created

with this change that will only allocate RMF III data

sets with RMFV DDNAME prefixes.

Thanks to Tom Drager, Aurora Health Care
Change 33.193 ANALDSET abend IEC145I 413-04 with DDNAME=ADDPROG because

ANALDSET the DATA step inserted by Change 32.187 broke the logic

Aug 19, 2015 for UNIT=AFF by trying to read and write to and from the

same tape device.

Thanks to Randy Hewitt, HP Canada, CANADA.
Change 33.192 -CICS/TS 5.3 Beta added two new variables to CICSTRAN that

UTILEXCL caused UTILEXCL to report UNKNOWN WBJSNRQL and WBJSNRPL

VMAC110 fields, but the IMACEXCL it created has a syntax error,

Aug 18, 2015 And, since the two fields were INSERTED, the MXG INPUT

without IMACEXCL caused subsequent fields to be invalid

as they were misaligned. Now, 70/378/3376 are expected

values for 5.3 default SMFPSRVR, MCTSSDCN, and MCTSSDRL.

(Other values will generate the RUN UTILEXCL messages.)

-The CICSRDQU records have new reserved fields inserted,

that caused misalignment.

=====================================================

CICS/TS 5.3 IS STILL IN BETA, with final GA is Sep 31,

so IBM is still free to make other changes.

=====================================================

Thanks to Paul C. Gordon, Bank of America, USA.
Change 33.191 UTICBLDP error message COMPBL HAS TOO MANY ARGUMENTS was

UTILBLDP due to an unneeded second COMPBL invocation for MACKEEPX.

Aug 18, 2015 The second execution was removed, but the error was also

triggered by comments with "* comment text ;" syntax, and

using " /* comment text */ " syntax also circumvented the

error. In general, that second syntax is more robust,

but in this case, placing the comments OUTSIDE the MACRO

circumvents the need to parse either comment syntax.

Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.190 While the WORK.TY115215 dataset is created by TYPE115,

VMAC115 using TYPS115 did not create PDB.TY115215 because the

VMXGINIT _STY115X dataset sort macro for TY115215 was not added

Aug 17, 2015 in the _S115 "product" sort macro for SMF type 115s.

This caused dataset TY115215 to not be listed in DOCVER.
====== Changes thru 33.189 were in MXG 33.08 dated Aug 17, 2015=========
Change 33.189 Support for z/OS 2.2 (COMPATIBLE, but LOTS NEW STUFF):

BUILD005 -TYPE0203: Support for new ID=2 SUBTYPE=1 and 2 records

EXTY4227 create two new datasets in VMAC0203:

EXTY9037 DDDDDD DATASET DESCRIPTION

FORMATS TY0201 TYPE0201 TYPE 2 SUBTYPE 1 SIGNATURE GROUP

IMAC42 TY0202 TYPE0202 TYPE 2 SUBTYPE 2 SIGNATURE INTERVAL

IMAC90A -TYPE1415: Change 33.026 added support for LONG WANTED new

VMAC0203 variables SYSPLEX JESNR JCTJOBID TYPETASK, but the pre-

VMAC104 GA SMF Manual had the order of SYSPLEX/JCTJOBID while

VMAC106 the actual order is JCTJOBID/SYSPLEX and the typo will

VMAC1415 be corrected for the Sub-type 3 record.

VMAC30 -Sub-type 5, length is 72 but 70 in SMF Manual; two bytes

VMAC42 are skipped

VMAC6156 -SMF14ALIAS now created.

VMAC74 -SMF14DSVER value is '01'x but bits 0, 1, 2, are listed

VMAC90A in the SMF Manual. Await IBM answer.

VMAC99 -JOB variable has un-printable characters in the 14/15s,

VMACCTLG but valid characters are in JOB variable in 30s, in pre-

VMXGINIT GA data. Await IBM answer. SMF14ESL=26 STY=5 (old

Mar 8, 2015 length) protected.

Jun 8, 2015 -TYPE26J2: New IBM JCTJOBID=:'G' value will set the MXG

Jul 21, 2015 TYPETASK='JOBG', only in TYPE26J2 Purge Records for a

Jul 24, 2015 JOBGROUP's logging job's purge, which is the only place

Aug 4, 2015 that 'G' value is externalized in SMF records.

Aug 17, 2015 -TYPE30 : New ABEND='EVICT' value set in TYPE30 for jobs

Mar 1, 2016 evicted with $EJ,STEP,HOLD.

-TYPE42: Change 33.026 added support for new TYPE4227

dataset provide the VTOC AUDIT LOG with these variables:

JCTJOBID ='SMF42RNJO*JOB NUMBER'

JESNR ='JES*NUMBER'

TYPETASK ='TYPE*OF*TASK;

SMF42RIND ='SMF42RIND*RECORD*INDICATOR'

SMF42RSEEK='SMF42RSEEK*VTOC*TRACK*ID'

SMF42RSRCH='SMF42RSRCH*VTOC*RECORD*ID'

SMF42RCMDS='SMF42RCMDS*CCW*COMMAND*CODES'

SMF42RUPSW='SMF42RUPSW*CALLERS*ADDRESS'

SMF42RUTOK='SMF42RUTOK*USER*SECURITY*TOKEN'

SMF42RRSV ='SMF42RRSV*DEVICE*IS*RESERVED?'

SMF42RKEY ='SMF42RKEY*DSCB KEY*DATASET*NAME'

SMF42RDSC ='SMF42RDSC*DSCB*DATA*FIELD'

SMF42RACT ='SMF42RACT*ACTIVITY*TYPE'

with these possible activities in SMF42RACT that are

decoded by $MG042VT format:

'D***'='D***:DFSMS ACTIVITY'

'DCVF'='DCVF:CVAFDIR'

'DCRE'='DCRE:DADSM DATASET CREATE'

'DEXT'='DEXT:DADSM DATASET EXTEND'

'DPAR'='DPAR:DADSM DATASET PARTIAL RELEASE'

'DREN'='DREN:DADSM DATASET RENAME'

'DDEL'='DDEL:DADSM DSCB SCRATCH'

'DUPD'='DUPD:DADSM DSCB UPDATE'

'DFRG'='DFRG:DFSMSDSS DEFRAG'

'DCON'='DCON:DFSMSDSS CONSOLIDATE'

'DDMP'='DDMP:DFSMSDSS DUMP'

'DRST'='DRST:DFSMSDSS RESTORE'

'IOBE'='IOBE:IOBE NOT PROVIDED'

'USER'='USER:IOBEUSER NOT SPECIFIED'

-TYPE42: Support subtype 5/6 APAR OA44322/OA44319 CMR+

and new microsecond metrics was added in Change 32.113.

-TYPE74: Change 32.305 added support for new TYPE 74

variables: R744MNEL R744MNEC R744NSRK

-TYPE90A: Updated for new Type 90 subtype 37 to create

new TYPE9037 dataset that reports any changes to APF

status. The RACF UTOKEN has '55'X values in SMF data

because it's value is "MASKED", i.e., encrypted, while

MXG expected the "UNMASKED" values that are in UTOKEN in

other SMF records (42, 80, 119). The existing SMF 90

subtypes 29 and 31 also contain the MASKED UTOKEN, but

IBM Development has stated their intention to change to

UNMASK the UTOKEN in all three of those 90 subtypes.

HOWEVER: SEE CHANGE 33.282 - MXG now "unencrypts".

The RACROUTE REQUEST=TOKENMAP can do the "unmasking",

and can be used even on a system that was not the one

on which the SMF record was created, but that can only

be used on z/OS; even there it would take SIGNIFICANT

effort to issue a RACROUTE from within a SAS data step.

But since the data length is 80 bytes either way, and

the data is not secret, it really needs to be UNMASKED

to be of value, so IBM's future correction is welcome.

-TYPE90A: Two variables added to TYPE9037 dataset.

Formats added to TYPE9037 variables.

-TYPE99 : Five variables added to TYPE9912 dataset.

-TYPE104: Platform Types that create SMF Type 104 records

are expanded and format updated:

VALUE MG104PT

0='0:AIX ON SYSTEM P'

1='1:LINUX ON SYSTEM X'

2='2:LINUX ON Z SYSTEM'

3='3:WINDOWS ON SYSTEM X'
-TYPE106: Support for new ID=106 SUBTYPE=1 and 2 records

create two new datasets in VMAC106

DDDDDD DATASET DESCRIPTION

TY1061 TYPE1061 BCPII HWISET API CALLS

TY1062 TYPE1062 BCPII HWICMD API CALLS

Mar 1, 2016: Incorrect length for SMF6ASDL, corrected

to input 4 bytes.

-VMACCTLG and VMAC6156 were updated Nov 27, 2014.

Support for GDGE, GDG Extended GDGLIMIT=999 in z/OS 2.2.

New variable GATEXTND='E' flags the extended mode, new

variables GATLIMTE/GATCNTE are INPUT but also kept in the

existing GATLIMIT/GATCNT to preserve existing reports.

Some overlooked flag variables in the 05 Catalog Segment

are now decoded and kept in datasets TYPE6156 (from SMF

(type 61, 65, 66) and TYPECTLG (from the IDCAMS EXPORT

CATALOG flat file). These are all the 05 fields now:

GATALLOC='GATALLOC*FIFO OR*LIFO?'

GATCNT ='GDG*COUNT'

GATDELET='DELETE*WHEN*LIMIT*EXCEEDED*0=OLD*1=ALL?'

GATEXTND='GATEXTND*EXTENDED*OR CLASSIC?'

GATEXTNO='GATEXTNO'

GATGEN ='GATGEN '

GATLIMIT='MAXIMUM*GDS*ENTRIES*IN GDG*BASE'

GATLIMTE='EXTENDED*GAT*GATLIMIT'

GATPURGE='GATPURGE*YES OR*NO?'

GATSCRTH='SCRATCH*FORMAT 1*DSCB*0=NO*1=YES?'

GATVER ='GATVER '

GATWRAP ='GATWRAP '

GDGATTR ='GDGATTR'

-BUILD005 protects for TYPETASK='JOBG' in JCTJOBID.

Change 33.188 TMON/CICS Version 4.0, these four MONITASK variables were

VMACTMO2 divided by 4096, TWICE:

Aug 13, 2015 TASTCPUT TASTCPOT TACNTRTM TACNTWTM

and these MONIAMQ variables were NOT divided because the

test was GT 4 and it should have been GE 4.

TAAMQOPT TAAMQCLT TAAMQGTT TAAMQPTT TAAMQP1T

TAAMQIQT TAAMQSTT

This change is REQUIRED to support TMON/CICS Version 4.

Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.187 DB2 T102S106 didn't keep variables QWP4RSMX and QWP4ACAN

VMAC102 and these zparms were not input.

Aug 14, 2015 QWP1CSMF='SMFCOMP'

Aug 20, 2015 QWP1FLG2='QWP1FLG2*FLAG*BITS'

QWP1LOGT='LOG*CHECKPOINT*TYPE'

QWP4ABVC='QWP4ABVC*SERVICEABILITY'

QWP4ACAN='QWP4ACAN*SERVICEABILITY'

QWP4CGAA ='GET_ACCEL_ARCHIVE*0=NO*1=YES*/

QWP4CQAC ='QUERY*ACCELERATION'

QWP4EXQRY ='QWP4EXQRY'

QWP4FCPPRC='FLASHCOPY*PPRC'

QWP4QACO ='QUERY*ACCEL*OPTIONS'

QWP4RFRP ='REC_FASTREPLICATION'

QWP4RLPR ='REORG*LIST*PROCESSING'

QWP4RPSN ='REORG*PART*SORT*NPSI'

QWP4RSMX='QWP4RSMX*SERVICEABILITY'

QWP4STMN ='REALSTORAGE*MANAGEMENT'

QWP4WFRD ='MAX RID*BLOCKS*TEMP STG*PER RID LIST'

QWP4_BIF_COMPAT='BIF*COMPATIBILITY'

QWP9DDFCIP='DDF COMPAT*IDENTITY*PRIOR VERSION*NNR'

Thanks to Lai Fai Wong, Bank of America, USA.
Change 33.186 -An INCOMPATIBLE z13 ERROR, only in SMT-MODE, and only if

VMAC7072 a CP engine is varied online, is now corrected. When a

Aug 16, 2015 a z13 in SMT mode varied a new CP online, MXG did not see

the new engine, causing PDB.TYPE70 and PDB.TYPE70EN to

be wrong, with incorrect PCTCPUBY and NRCPUS=. and no

dispatch times for the new CP engine in PDB.TYPE70.

An IBM error is only partially responsible: after the

VARY, the value for SMF70CIX in the PR/SM LP Data Section

is incorrect (1, for CP, instead of 6, for zIIP) in both

of the zIIP sections for the second zIIP engine, causing

MXG to identify those zIIPs as CP Engines, mismatching

the engines in the CPU Data Section. That error is

circumvented by revising MXG to use the SMF70TYP value

from the CPU data section (which is clearly what IBM had

to use in their RMF reports). A second error was MXG's:

the new CP Engine PR/SM section was located AFTER those

zIIP sections, but MXG's original SMT logic was correct

only when all CPs preceded the zIIPs. That incorrect

MXG logic was revised to now be order independent.

-TYPE70PR does NOT contain SMT variables, those data are

only output in PDB.TYPE70EN since they can only be

populated from "this" system's TYPE70 records.

Thanks to Douglas C. Walter, CitiCorp, USA.

Thanks to Brent Turner, Citigroup, USA.

Change 33.185 -Labels for TYPE30 ZEDC variables with _INF_/_DEF_ are now

FORMATS spelled out as INFLATE and DEFLATE.

VMAC30 -TYPE74 subtype 9 DIVIDE BY ZERO caused by R749FRQC=1 is

VMAC74 eliminated by changing test to R749FRQC GT 1 since more

Aug 11, 2015 than one instance is required to calculate STD (Standard

Aug 17, 2015 Deviation) statistic.

Aug 20, 2015 New variable PCTCRDBY added to TYPE749 dataset for card

Aug 30, 2015 busy percentage.

-TYPE74 variables used to create SSQ (Sums of Squares) are

no longer kept since the STD variables are calculated.

-Variable R749DFMT is now labeled 'PCIE*FUNCTION*TYPE' and

is decoded by MG074DF format to describe which sets of

variables are populated:

0='0:DMA COUNTERS'

1='1:ETHERNET INTERFACE'

2='2:WORK UNITS'

However, records with SMF749DL=16 do not contain R749DFMT

so R749DFMT will be missing, causing all of these sets of

variables to have missing values:

0: R749DMAR R749DMAW R749DBYR R749DBYT R749DPKR

1: R749DBYR R749DBYT R749DPKR R749DPKT

2: R749DWUP R749DWUM

SMF749DL=40 is required for PCIE Function Type Data to

actually exist.

-Aug 17: INVALID type 30 zEDC segments (SMF30USO points

to the middle of the EXCP Section, or points beyond the

end of the record) were just confirmed by IBM support,

and occur because the SMF30USN count is not being reset

to zero in the "Continuation", MXG MULTIDD='Y' records.

The MXG Logic now only inputs the SMF30USO segment when

MULTIDD=' ', i.e., only for the base/original record.

Aug 25: IBM APAR OA48717 will correct the invalid zEDC

triplet information in the TYPE30 record.

-Aug 20: zEDC Compression Ratios for Inflate/Deflate are

created and kept in all TYPE30 datasets.

-Aug 30: zEDC Compression Ratios for Inflate/Deflate are

created and kept in TYPE749 datasets.

Thanks to Joseph J. Faska, DTCC, USA.

Change 33.184 Support for SYNCSORT Release 1.4 (INCOMPATIBLE). Change

VMACSYNC 33.102A added support for Release 2.1, which has the same

Aug 11, 2015 SMF data, so this change now tests SYNCVAL GE 1.4 to now

populate READTIME and many other variables that are wrong

without this change.

Thanks to Joseph J. Faska, DTCC, USA.

Change 33.183 Support for MAR Hitachi Command Suite Mainframe Analytics

EXMAR01 Recorder, user SMF records creates these dataset:

EXMAR02

EXMAR03 DDDDDD MXG MXG

EXMAR04 DATASET DATASET DATASET

EXMAR05 SUFFIX NAME LABEL

EXMAR06

IMACMAR MAR01 MARST01 LOST SMF INFORMATION

TYPEMAR MAR02 MARST02 LDEV INFORMATION

TYPSMAR MAR03 MARST03 MPB INFORMATION

VMACMAR MAR04 MARST04 PRGP INFORMATION

VMXGINIT MAR05 MARST05 PORT INFORMATION

Aug 11, 2015 MAR06 MARST06 MP USAGE TO TWENTY
Change 33.182 -Major enhancement for character data filtering for ASI

ADOCRMFV RMF Monitor III table entries and other improvements.

ASMRMFV -These filters are intended for building ad hoc MXG RMF

Aug 1, 2015 III PDBs for studies avoiding the overhead of generating

a full ASI table based PDB. They control which ASI table

entries are output to the RMFBSAM file.

-10 new filters are added to support ASI entry selection

from this table to the RMFBSAM output file. These

filters are effective only if the ASI table is selected.

They are applied in the order shown when multiple

different keywords are used.
New Keyword Aliases

------------ --------------------------------------

ASISUBSYS= ASISUB= TYPETASK=

ASIWORKLOAD= ASIWKLD= ASIWNM= ASIWL=

ASIRESGROUP= ASIRESGRP= ASIGNM= ASIRG=

ASISRVCLASS= ASISCLASS= ASICNM= ASISC=

ASIRPTCLASS= ASIRCLASS= ASIRNM= ASIRC=

ASIJOBCLASS= ASIJCLAS= ASICLASS= ASIJC=

ASIJOBNAME= ASIJOBNA= ASIJOBNM= ASIJOB= ASIJN=

ASIJESID= ASIJESNO= ASIJESNUM= ASIJESNR= ASIJID=

ASIAND None

ASIOR None

-TUTORIAL:

Ranges of the form keyword=first:last may be used with

any of the above keywords except ASIAND and ASIOR. The

colon character ':' is required for a range

specification.
However, single values may be specified for a range

simply as keyword=first and in this case the colon ':'

can be omitted.
All ASI entries GE the first value and LE the last value

are selected for output to the RMFBSAM file. Ranges may

not be wild carded only patterns. The first value in a

range may not be GT the last value or an error is noted.

Patterns may also be used with any of the above keywords

except ASIAND and ASIOR and include one or more wild card

characters to match the respective ASI data field.
Wild

Card Matches

---- -------------------------------------------------

* 0 or more characters

% 1 Non-blank character

+ 1 Numeric character (0-9)

_ 1 Alphabetic character or _ (a-z, A-Z, _)

. 1 National character (@, #, $)

! 1 Special character (not a-z, A-Z, 0-9, @, #, $)

? A blank string if used by itself

? 1 Blank character (X'40') if used with any other

characters

See Section 25 in the ADOCRMFV member for more details on

usage of ranges and patterns.

-ASISUBSYS= selects ASI entries by host Subsystem Name:

APPC, JOB, OMVS, STC, TSU, UNKN.

More than one subsystem may be requested. Ranges and/or

patterns may also be used, but are generally unnecessary

given the limited possible choices. Only those IBM

subsystems defined in the ASI table are supported.

Subsystem names are validated. The default is

ASISUBSYS=ALL.

For ease in coding and recall there are several value

aliases allowed with ASISUBSYS=.

Subsystem

Name Supported Values

--------- -----------------------------------------

APPC A, AP, APP, APPC, AS, ASC, ASCH

JOB J, JO, JOB, JOBS, B, BA, BAT, BATC, BATCH

OMVS O, OM, OMV, OMVS

STC S, ST, STC, STA, STAS, STASK, STASKS

TSU T, TS, TSO, TSU, TSUS

UNKN U, UN, UNK, UNKN, UNKNO, UNKNOW, UNKNOWN,

UNKNOWNS
-Examples for ASISUBSYS=

ASISUBSYS=JOB selects only Batch jobs.

ASISUBSYS=J:S selects Batch jobs, OMVS address spaces,

and Started Tasks because these all fall into the range.

ASISUBSYS=JOB ASISUBSYS=TSO selects Batch job and

TSO user address spaces.

-ASIWORKLOAD= selects ASI entries by 8 character WLM

Workload Name. Both ranges and patterns with wild card

characters may be specified. Up to 64 ranges and 64

patterns are supported. The default is ASIWORKLOAD=ALL.

-Examples for ASIWORKLOAD=

ASIWL=PROD:TEST selects all WLM Workloads GE 'PROD' and

LE 'TEST' using a range. Note use of keyword alias

ASIWL.

ASIWORKLOAD=PROD* selects only address spaces with a WLM