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

-Boole informed me that CONTROL-D is a New Dimension Co

product (although it is marketed by Boole in Europe), so

I have updated that product, as well as Boole's products

in member YEAR2000.

Thanks to whoever told Boole marketing about YEAR2000 on www.MXG.com!

Change 15.178 Example macro definitions for _KCICTRN that will keep

IMACCICS only CICSTRAN variables that are needed for ASUMCICS or

Aug 1, 1997 ASUMUOW have been added to member IMACCICS (although they

are commented out). See CICS Technical Note in MXG

Newsletter THIRTY-TWO or comments in IMACCICS itself.

Thanks to Mark Cohen, ???, ITALY.

Change 15.177 -Typos: after DDD=MOD(MVLCDATE ... change IF 0 LE DDD to

VMACEDGS IF 0 LT DDD. Remove the second occurrence of MVEXPDT in

Aug 1, 1997 the FORMAT statement.

-Logic change. DFSMS/rmm variables MVEXPDT and MKDELDAT

can have value 1999366 as a "never expire" date, but that

is an invalid SAS date. MXG's DCOLLECT algorithm is now

used for these values, and the date is set to the future

date in year 2099 (and the original value is available in

character variable MVEXPDTO for MVEXPDT, although there

is no corresponding character variable for MKDELDAT):

IF DDD GT 366 OR (YY=99 AND DDD GE 365) THEN DO;

MVEXPDT='31DEC2099'D;

END;

Thanks to Peter Young, University of Toronto, CANADA.

Change 15.176 Invalid Catalog Cell '05'x caused INPUT STATEMENT EXCEED

VMACCTLG error. The cell began at byte 279, with Length of Cell

VMAC6156 '2E'x (46) bytes, and at byte 284 the count of four-byte

Aug 1, 1997 segments following is '5C'x (92), so MXG attempted to

read 92*4=368 bytes of GAT segments, but there were only

40 bytes left in the record. To circumvent this IBM

error, MXG had to add code to validate that the number of

segments is consistent with the cell length:

Change DO _I_=1 TO GATCNT;

to IF GATCNG*4 LE SKIP THEN DO _I_=1 TO GATCNT;

and after the END; statement for that DO group, insert:

ELSE DO;

INPUT +SKIP @;

SKIP=0;

NB615605+1;

IF NB615605=1 THEN DO;

PUT // ' *** INVALID CATALOG CELL 05 SKIPPED.'/

_N_= SMFTYPE= SYSTEM= JOB= LENTHIS= GATCNT= COL= ;

LIST;

END;

END;

Thanks to Shana Bereznay, Southern California Edison, USA

Change 15.175 CICS formats $MGCICDL and $MGCICDS that decode variables

FORMATS LDGDSAIN, SMDDSAIN, SMSDSAIN, and SMTDSAIN printed trash

Jul 29, 1997 because the syntax 01X= was used (a numeric hex value)

instead of the '01'X syntax that is needed for character

values. SAS could not raise an error condition, because

(due to legacy considerations) both quoted and unquoted

strings are valid syntax. Adding quotes corrects.

Thanks to Larry Gray, Lowe's Companies, Inc, USA.

Change 15.174 Using ANALCNCR with an INTERVAL greater than 24 hours

ANALCNCR produced valid results, but cause a very large number of

Jul 29, 1997 unnecessary observations to be created in the work file,

because SYNCINTV=YES was set by default. Now, the large

interval value will be recognized and SYNCINTV=NO will be

forced (and a note to that effect printed on the log).

Thanks to Clark Jennings, Reynolds Metals Company, USA.
Change 15.173 A question on MXG-L concerning how to merge DB2 Trace

ANALDBTR records with DB2ACCT and CICSTRAN data has resulted in

Jul 29, 1997 an new example program in member ANALDBXX. The example

uses ANALDBTR, but an new options, UOWSORT, had to be

created in ANALDBTR. UOWSORT=YES causes variables

NETSNAME and UOWTIME to be kept in all dataset pairs

created by ANALDBTR, and also causes those variables to

be added to the BY list in each sort. This example will

likely become a new option in ANALDB2R in the future,

but this working example is provided for use now.

Member ANALDBXX removed when ANALDB2R was updated.

Thanks to Michael Frey, COMLAB GmbH, GERMANY.

Thanks to Chuck Hopf, MBNA, USA.
Change 15.172 Support for Xerox's XPSM Version 2 (Xerox Print Services

VMACXPSM Manager) Host Accounting Record (INCOMPATIBLE). The new

ZMACXPSM record is a complete restructure of the original record,

Jul 29, 1997 but contains much new and useful information if you are

using XPSM. Among the major additions are:

- The record now contains all fields in IBM's type 6

record for PSF, and MXG uses the same variable names

that you know from TYPE6 processing

- Unlike IBM's type 6, the XPSM V2 record contains the

Account Fields from the Job card, plus a "Department

Account", so it is not necessary to merge TYPEXPSM

with type 30 data to charge back XPSM printing, and

you can account for jobs printed after the job purge

record has been created (e.g., output sent to remote

print servers).

- Repeated segments contains multiple names of Forms,

Overlays, Fonts, Images, Templates, and Colors.

MXG keeps first eight values (three for colors).

- Printer setup names JDL and JDE used.

- Remote Server section provides timestamps of begin and

end of transmission and begin/end of printing.

- MVS Host CPU time (TCB,SRB,RCT,IPT,HPT) are captured.

- MVS I/O SSCH counts and spool size for each DASD and

Printer device used are available, although MXG has

only implemented capture of the totals (a dataset for

each DD will be implemented when requested).

- CPU of cost of data stream transformation (eg, LCDS to

PCL) is captured.

- Outage and change of state information is provided.

Thanks to Dan Kaberon, Hewitt Associates, USA.

Change 15.171 HSM dataset DGN's variable DGNDCL was blank because the

JCLHSM INPUT DGNDCI should have been INPUT DGNDCL. Several

VMXGHSM non-existent variables were removed from the KEEP= list

Jul 28, 1997 for datasets MCP and DGN. The now-nonexistent option

DQUOTE was removed from JCLHSM. The %VMXGHALL macro

used in the MXG QA job, was updated so that all of the

HSM datasets are created; this accounts for new datasets

BCR, BVR, DCL, DCR, DGN, MCB, MCC, MCM, MCP, MCPDGN, and

MCT now being listed in member DOCVER.

Thanks to Peter Young, University of Toronto, CANADA.

Change 15.170 Support for OS/390 Version 2 Release 4.

VMAC1415 -TYPE1415: Variables PROGRAM and STEPNAME were added:

VMAC26J2 (MXG's ANALDSET, which is still needed to correctly de-

VMAC30 accumulate EXCP counts from 14/15's has always picked up

EXTY4237 PROGRAM and STEPNAME, but having them directly in these

IMAC42 records is long overdue!).

VMAC71 -TYPE26J2: New workload management section added:

VMAC7072 JOBMODE0='JOB RAN*IN*MODE=WLM?'

VMAC42 JOBMODE1='JOB RAN*BECAUSE*OF $S J?'

VMAC74 SMF26WCL='SERVICE*CLASS AT*EXECUTION'

Jul 23, 1997 SMF26WIN='JOB*INDICATORS'

SMF26WJC='JOB*CLASS'

SMF26WOC='ORIGINAL*SERVICE*CLASS'

SMF26WSE='SCHEDULING*ENVIRONMENT'

-TYPE30: datasets TYPE30_V, TYPE30_4, TYPE30_5 and

TYPE30_6 have important new data:

-New DASD-only Connect/Disconnect/Pending time plus

SSCH counts for ASID plus Dependent Enclaves and for

Independent Enclaves (added by OS/390 R1.3).

SMF30AIC='DASD CONNECT*ASID PLUS*DEPENDENT'

SMF30AID='DASD DISCONNECT*ASID PLUS*DEPENDENT'

SMF30AIS='DASD SSCH*ASID PLUS*DEPENDENT'

SMF30AIW='DASD PEND+CU*ASID PLUS*DEPENDENT'

SMF30EIC='DASD CONNECT*INDEPENDENT*ENCLAVES'

SMF30EID='DASD DISCONNECT*INDEPENDENT*ENCLAVES'

SMF30EIS='DASD SSCH*INDEPENDENT*ENCLAVES'

SMF30EIW='DASD PEND+CU*INDEPENDENT*ENCLAVES'

-CPU for Dependent Enclaves is recorded:

CPUDETTM='DEPENDENT*ENCLAVE*CPU TIME'

-Residency time in Page-Seconds in ESTORE was added,

but CSTORE residency is not (yet?) provided:

RESESFTM='ESTORE*RESIDENCY*PAGESECS'

-New Scheduling Environment (when WLM owns Initiators

and adds/drains INITs to meet Service Objectives!)

add several important durations and flags:

SMF30HQT='JOB*HOLD*TIME'

SMF30JQT='JOB*PREPARATION*TIME'

SMF30PFF='JOB INIT*WAS FORCED*BY OPERATOR?'

SMF30PFL='SCHEDULING*ENVIRONMENT*NAME'

SMF30PFR='SRVCLASS*WAS MODIFIED*DURING*EXECUTION?'

SMF30PRJ='SRVCLASS*WAS MODIFIED*PRIOR TO*INIT?'

SMF30RQT='INELIGIBLE*FOR*EXECUTION*TIME'

SMF30RTR='JOB*HAS*BEEN*RESTARTED?'

SMF30SQT='ELIGIBLE*FOR*EXECUTION*TIME'

-TYPE42: new subtype 9 creates new dataset TYPE4237

for every B37/D37/E37 (out of space) ABEND. The record

is useful for tracking these abends, but I have asked

for the record to be (optionally) written when datasets

are extended (so you could track those jobs/datasets that

are going to abend before they do!). Variables are:

DISP ='DISPOSITION'

DSNAME ='DATA SET NAME'

DSORG ='DSORG'

JOB ='JOB NAME*OR*TSO USER'

LOCLINFO='LOCAL*INSTALLATION*FIELD'

READTIME='READ-IN*OR LOGON*EVENT'

S42ABEND='S42FLAGS*B37 OR*D37 OR*E37?'

S42ADRLH='S42ADRLH*AVERAGE*BLOCK*LENGTH'

S42ASSAT='S42ASSAT*SECONDARY*ALLOCATION*AMOUNT'

S42ASYID='S42ASYID*SYSTEM*ID'

S42DCNME='S42DCNME*DATA*CLASS*NAME'

S42MCNME='S42MCNME*MANAGEMENT*CLASS*NAME'

S42NEXT ='S42NEXT*NUMBER OF*EXTENDS*THIS VOL'

S42SCNME='S42SCNME*STORAGE*CLASS*NAME'

S42TNTRK='S42TNTRK*TOTAL*TRACKS*THIS VOLUME'

S42UCBTP='S42UCBTP*UCB*TYPE'

STEPNR ='STEP*NUMBER'

VOLSER ='VOLUME*SERIAL*NUMBER'

-TYPE71: new counts of frames in CSTORE/ESTORE includes

available, and low/medium/high impact frames in memory:

CSFRAVMN='SMF71CAM*MIN*CSTORE*FRAMES*AVAILABLE'

CSFRAVMX='SMF71CAX*MAX*CSTORE*FRAMES*AVAILABLE'

CSFRAVAV='SMF71CAA*AVE*CSTORE*FRAMES*AVAILABLE'

CSFRLOMN='SMF71CLM*MIN*CSTORE*LOW IMPACT*FRAMES'

CSFRLOMX='SMF71CLX*MAX*CSTORE*LOW IMPACT*FRAMES'

CSFRLOAV='SMF71CLA*AVE*CSTORE*LOW IMPACT*FRAMES'

CSFRMEMN='SMF71CMM*MIN*CSTORE*MED IMPACT*FRAMES'

CSFRMEMX='SMF71CMX*MAX*CSTORE*MED IMPACT*FRAMES'

CSFRMEAV='SMF71CMA*AVE*CSTORE*MED IMPACT*FRAMES'

CSFRHIMN='SMF71CHM*MIN*CSTORE*HIGH IMPACT*FRAMES'

CSFRHIMX='SMF71CHX*MAX*CSTORE*HIGH IMPACT*FRAMES'

CSFRHIAV='SMF71CHA*AVE*CSTORE*HIGH IMPACT*FRAMES'

ESFRAVMN='SMF71EAM*MIN*ESTORE*FRAMES*AVAILABLE'

ESFRAVMX='SMF71EAX*MAX*ESTORE*FRAMES*AVAILABLE'

ESFRAVAV='SMF71EAA*AVE*ESTORE*FRAMES*AVAILABLE'

ESFRLOMN='SMF71ELM*MIN*ESTORE*LOW IMPACT*FRAMES'

ESFRLOMX='SMF71ELX*MAX*ESTORE*LOW IMPACT*FRAMES'

ESFRLOAV='SMF71ELA*AVE*ESTORE*LOW IMPACT*FRAMES'

ESFRMEAV='SMF71EMM*MIN*ESTORE*MED IMPACT*FRAMES'

ESFRMEMN='SMF71EMX*MAX*ESTORE*MED IMPACT*FRAMES'

ESFRMEMX='SMF71EMA*AVE*ESTORE*MED IMPACT*FRAMES'

ESFRHIMN='SMF71EHM*MIN*ESTORE*HIGH IMPACT*FRAMES'

ESFRHIMX='SMF71EHX*MAX*ESTORE*HIGH IMPACT*FRAMES'

ESFRHIAV='SMF71EHA*AVG*ESTORE*HIGH IMPACT*FRAMES'

Note of Sep 16, 1997: IBM will not publish the UIC

values that define High, Medium, or Low Impact,

because "the UIC ranges depend on whether the system

is in goal or compatibility mode and several OPT

settings. These are values that may change in the

future. The idea of reporting these buckets was

just to get a high level view of how much stress

there is on the system's storage."

-TYPE72: support for WLM Managed Initiators added new

total sample count that includes batch queue delays,

so the calculation of VALDSAMP now also includes any

batch queue delays; batch queue delay is measured as are

three components, and the DASD IOS Queue Time is also

measured in dataset TYPE72GO:

PCTDLTDQ='TOTAL*(INCLUDES BATCH)*DELAY*SAMPLES'

PCTEXTSA='TOTAL*EXECUTION*SAMPLES'

R723CDQT='TOTAL*BATCH*QUEUE*DELAY*TIME'

R723CADT='INELIGIBLE*AFFINITY*DELAY TIME'

R723CIQT='INELIGIBLE*OTHER RESOURCE*DELAY TIME'

R723CCVT='JCL*CONVERSION*DELAY TIME'

R723CIOT='DASD*IOS*QUEUE TIME'

And dataset TYPE72DL has one new variable:

R723RWNL='STATE WITH*WAIT FOR*NEW LATCH'

-TYPE74: Coupling Facility dataset TYPE74CF now has the

model, version and level information:

R744FMOD='COUPLING*FACILITY*MODEL'

R744FVER='COUPLING*FACILITY*VERSION'

R744VLVL='COUPLING*FACILITY*LEVEL'

An additional change to BUILDPDB to add the new hold

delays (from which TYPRUN=HOLD time can be calculated)

will be available in the next version of MXG.

Revised, Nov 11, 1998: Enhancements to System Logger SMF

type 88 and OAM SMF type 85 records were supported in

MXG 16.06, Changes 16.265 and 16.255.

Change 15.169 Inconsistencies between MVS and ASCII versions of SAS

VMACOPC prevented some MXG members from being executable on the

VMXGINIT ASCII platform. While these members are not likely to

VMXGVTOC be used on the ASCII platforms, by making their code

Jul 22, 1997 transparently execute on all SAS platforms, I can run

the MXG QA stream anywhere, so changes were made:

-ASCII SAS does not accept RECFM=VBS, and MVS SAS does

not accept RECFM=S370VBS, so macro variable VMXGVBS

is now defined in member VMXGINIT to allow member

VMACOPC to execute. All other usage of VBS was already

protected by other means.

-ASCII SAS does not accept INFILE options CCHHR VTOC so

a local %MACRO VMXGCHR is created in VMXGVTOC (even

though that is a very archaic member).

Change 15.168 No observations in NETSPY dataset NSPYTIC3 because the

VMACNSPY logic inside NSPYREC='N' code to identify subtype used

Jul 22, 1997 either NSPNRECI or NSPNSUBT values, but the value '01'x

for NSPNSUBT exists in both Ethernet and TIC3 records, so

TIC3 observations were erroneously OUTPUT in NSPYETHR.

Now, all tests use ONLY variable NSPNRECI, but changing

ELSE IF NSPNRECI='06'X OR NSPNSUBT='01'X THEN ..

ELSE IF NSPNRECI='06'X THEN ...

will correct the immediate problem.

Also, the last alert in each record was not output in the

NSPYALRT dataset, and the second and later were corrupted

because the statement:

OFFNSPY=OFFNSPY-10;

that was just before the INCLUDE SOURCLIB(EXNSPYAL);

should not have been there and must be deleted.

Thanks to Mrs. Silvia Hug, RWG GmbH, GERMANY.

Thanks to Mr. Karl-Heinz Placht, RWG GmbH, GERMANY.
Change 15.167 MXG now protects all two-digit YY dates for year 2000.

IMACICBB Since IBM and other vendors have not expanded all of the

TYPEDMS two-digit YY dates, and since it is likely that some MXG

TYPEMON8 sites will still be back level on some of those products

TYPEMONI that are not year-2000 compliant, and since I could cover

TYPEPDL for the negligent products, I have extended Change 15.050

TYPETMON and have added logic to "Window" all dates that are not

TYPEVM year-2000 compliant. Years 00-59 will be set to 20xx

VMAC28 while years 60-99 will be set to 19xx.

VMACCTLD In some members, this protection was added using:

VMACIPAC IF YEAR(DATEPART(datetime)) LE 1959 THEN

VMACNSM datetime=datetime+YEARSECS;

VMACNSPY where RETAIN YEARSECS 3155673600; is used to store the

VMACODS number of seconds between 1Jan1900 and 1Jan2000.

VMACOPC In other cases, the protection was added using:

VMACQTRT IF YEAR(date) LE 1959 THEN date=date+YEARDAYS;

VMACRMDS where RETAIN YEARDAYS 14610 is used to store the number

VMACROSC of days between 1Jan1900 and 1Jan2000.

VMACSAR

VMACTMDB Member YEAR2000 has been updated to show which dates

VMACVMXP are truly year 2000 compliant (and the APAR which made

VMACXAM them so) and to show which dates are not compliant but

YEAR2000 are now protected by MXG Logic to support the year 2000.

Jul 20, 1997

Change 15.166 Support for Catalog Cell 'E7'x ("X" - Alias Cell) is now

EXCTLGE7 added to VMACCTLG so as to create new dataset CTLGE7 obs

IMACCTLG for each alias cell. In addition, the E7 cell will now

VMACCTLG be decoded in the optional logic in VMAC6156 (which only

VMAC6156 prints catalog cells on the SAS log).

Jul 18, 1997

Thanks to Michael Ayers, Wyeth Labratories, USA.

Thanks to Brian Cooper, Wyeth Labratories, USA.

Change 15.165 Support for new subtype 6 type 99 record creates new data

EXTY99U6 set TYPE99_6, called the "Goal Mode SMF" record by BGS.

VMAC99 The new subtype contains no new data (everything in it is

Jul 18, 1997 already in other subtypes of the type 99), but the new

record compacts the needed data in one subtype so that

you can afford to write that subtype 6 record and can

supress all other subtypes to reduce data volume.
Change 15.164 Variable MSGXRST is missing value because the ARRAY and

TYPEIMSA the DROP statement must be changed to read:

Jul 17, 1997 ARRAY CTR{54} CTR01-CTR54 ;

DROP CTR01-CTR54 I ;

i.e., change the 53's to 54's in those two lines.

Thanks to Kenneth D. Jones, SHL Systemhouse, NOVA SCOTIA.

Change 15.163 Support for DFSMS 1.4 adds (COMPATIBLY!) new fields:

VMACDCOL -Type 'A' - Dataset DCOLCLUS new variables:

Jul 17, 1997 DCACISZ ='NUMBER OF*BYTES IN*A CI'

DCACACIC='NUMBER OF*CI-S IN*A CA'

-Type 'V' - Dataset DCOLVOLS new variable:

DCVDPTYP='PHYSICAL*DEVICE*TYPE'

-Type 'M' - Dataset DCOLMIGS new variable:

DCVDPTYP='PHYSICAL*DEVICE*TYPE'

-Type 'B' - Dataset DCOLBKUP new variable:

UBFRVOL ='1ST SOURCE*VOL*OF BACKUP DATA'

-Type 'DC' - Dataset DCOLDC

Fifteen new DDCxxxxx construct variables.

-Type 'SG' - Dataset DCOLSG

Sixty-four status flags decoded & DSG32NAM corrected.

-Type 'VL' - Dataset DCOLVL

Ninety-six status flags decoded & DVL32NAM corrected.

-Type 'BC' - Dataset DCOLBC

Ninety-six status flags decoded & DBC32NAM corrected.

-Type 'DR' - Dataset DCOLDR

Sixty-four status flags decoded.

-Type 'LB' - Dataset DCOLLB

Sixty-four status flags decoded.

Change 15.162 Minor. Variable CPUSERF wasn not kept, and variable

RMFINTRV CPUHPTTM was not FORMATed nor LENGTHed.

Jul 16, 1997

Thanks to Bruce Widlund, Merrill Consultants, USA.

Change 15.161 Optional Omegamon/CICS DB2 variables OMBDESCN/OMBDESTM &

IMACICOB OMBEXECN/OMBEXETM were not labeled, nor were they kept in

VMAC110 CICSTRAN dataset.

Jul 15, 1997

Thanks to Harald Seifert, HUK-Coburg, GERMANY.
Change 15.160 ASUMUOW/IMACUOW are enhanced to allow large sites to send

IMACUOW the temporary sorted output of CICSTRAN/DB2ACCT to a

ASUMUOW DDname other than //WORK. Comments explain how.

Jul 15, 1997

Thanks to Chuck Hopf, MBNA, USA.
Change 15.159 IBM APAR OW13754 documents type 14/15 CRDATE and EXPDT

YEAR2000 support for year 2000 by allowing those one-byte binary

Jul 15, 1997 fields to have values 100 thru 255 to correspond to year

2000 thru 2155 (giving our descendants the opportunity

to make big bucks fixing the "Year 2155" problem). MXG

had assumed this solution, so no MXG code fix is needed.

Note that these julian dates will now print at 99363,

99364, 99365, 100001, 100002, etc.

Change 15.158 RACF type 80 RACFEVNT=22 and 59 are now supported, with

EXTY8022 new datasets TYPE8022 and TYPE8059. Segments for DTP for

EXTY8059 RACFTYPE=22, 24, 39, 40, 41, and 44 are now decoded. New

EXTY8X13 formats $MG080AF and $MG080UA are created by FORMATS.

EXTY8Y13 FORMAT MG808IA was updated so INTENT/ALLOW value 5 is now

EXTY8X24 decoded, TYPE8010 and TYPE8013 has SECLEVEL added.

FORMATS Dataset label for TYPE8018 is now PASSWORD COMMAND.

IMAC80A Several KW24xxxx variables were also corrected.

VMAC80A

Jul 14, 1997 For some RACF events, repeats of segments 21, 33, 34, 39,

Aug 24, 1997 40, 41, 42, and 44 are possible, but MXG kept only the

last instance. To repeat variables in the base TYPE80nn

or to create new TYPE8xnn dataset(s) depends on how many

repeats occur for a specific RACFEVNT; support for repeat

is added on a case-by-case basis when I receive test data

with multiple segments. Thus far, these instances of

repeated segments are supported as described:
-The many repeats of segment 21 in RACFEVNT=24 (SETROPTS)

are supported by observations in new TYPE8X24 data set,

keeping JOB READTIME SMFTIME SYSTEM as keys back to the

parent TYPE8024 dataset. The SETROPTS command creates

hundreds of repeated segments of questionable utility,

so creating an "Extra" dataset will save space.

-The second repeat of segment 33 in dataset TYPE8004 is

added as new variable RESNAME2 in that dataset. This

is a newname/oldname event, so only a second instance

needs to be supported.

-The six repeats of segment 44 in dataset TYPE8010 are

added as variables EV44FLG1-EV44FLG6, SEGNAME1-SEGNAME6,

and EV44TXT1-EV44TXT6, if more than 6 are found in the

RACFEVNT=10 record, a message will be put on the log.

For the other RACFEVNT's (11,12,13,20,21,22) only one

segment 44 has been observed, so only one is kept, but

a message will be put on the log if more are found.

-The many repeats of segments 40 and 41 in TYPE8013 create

new dataset TYPE8X13 for segment 40's (maximum of 20 has

been observed) and new dataset TYPE8Y13 for segment 41's

(maximum of 4 has been observed).

Thanks to Peter J. Lines, NatWest Bank, ENGLAND.

Thanks to Len Rugen, University of Missouri-Columbia, USA.

Thanks to Joseph J. Faska, Depository Trust, USA.

Change 15.157 Support for Shared Medical Services CICS application's

IMACCICS OASMON (SMS Online Architecture System) journal segments

IMACICSM creates new dataset CICSSMED. Observations are created

VMAC110 when records are found, with no user action required.

EXCICSME CICSSMED contains the OAS stack or program name and the

Jul 11, 1997 response time in type 110 subtype 0 SMF records without

having to enable CICSTRAN monitoring in your MCT.

Thanks to Kristyann Manske, University of Wisconsin-Milwaukee, USA.

Thanks to Kevin Hurst, Shared Medical Systems, USA.
Change 15.156 Variable DEVNR is now added to dataset TYPE74CA and is

VMAC74 equal to DEVN. The DEVN spelling was kept from the old

Jul 11, 1997 CACHE90 predecessor dataset so your old reports would

run from TYPE74CA, but DEVNR is the more common name in

all other MXG datasets, and is the variable name to use.

Thanks to MH, Allied Irish Bank, IRELAND.

Change 15.155 Cosmetic. Duplicate label statements were deleted in the

DOC members VMAC102, VMAC110, VMACAPAF, VMACCTLG, VMACHPSU,

Jul 10, 1997 VMACHPUX, VMACMWSU, VMACMWUX, VMACODS, VMACQAPM,

VMACTPX, and VMACXAM.

Thanks to Freddie Arie, Lone Star Gas, USA.
Change 15.154 Archaic members VMXGVTOC and VMXGVTOF did not create the

VMXGVTOC ZDATE variable in datasets INFO and VTOCINFO, but now the