CONFIG 8.068 SAS 6.06 options member added to MXG library.
DIFFHSM 8.260 HSM User SMF Record de-accumulation.
DOCDB2PM 8.112 Documentation of DB2PM-like reports in ANALDB2R.
DOCGRAF 8.274 SAS/GRAPH device support and MXG standards.
DOCTREND 8.113 Incompatible changes in MXG Trending implemented.
EXACFJR 8.047 ACF2 dataset ACF2JR may have deleted observations.
EXIDMTAS 8.105 IDMS Batch ACCOUNT1-3 fields decoded.
FMXGUCBL 8.009 Returns wrong value under SAS 5.18.
GRAFDB2 8.275 SAS/GRAPH analysis of DB2 data.
GRAFWORK 8.140 New graphic report of RMFINTRV workloads by hour.
IMACAAAA 8.281 Install aid describing which tailoring IMACs do what.
IMACACCT 8.133 Safer/Easier user tailoring of kept Account fields.
IMACICDB 8.177 CICS/ESA 3.1 Transaction DBCTL counters/clocks.
IMACPDB 8.048 Variables ABNDRSNC DIVRREAD DSSIZHWM TERMNAME added.
JCLDASD 8.264 MXG DASD (VTOC,VVDS) Space Management example.
JCLTEST 8.001 Options MACRO DQUOTE MWORK=28K required by MXG 7.7.
JCLTEST 8.025 WORK.DIRMACR REQUIRES MORE SPACE error condition.
JCLTREND 8.058 PROC SORT added to avoid not-sorted condition.
MONTHBLD 8.095 Syntax error under SAS 6.06 circumvented.
MVS 4.1 8.167 Support for MVS/ESA SP Version 4.1 and RMF 4.2.
MVS 4.2 8.224 Support for MVS/ESA SP Version 4.2 and RMF 4.2.1
NPM 8.038 NPM records from VM can be processed.
PRODUCTS 8.282 Documents MXG support by "product name/acronym"
RMFINTRV 8.216 SIO counts in RMFINTRV missing.
SAS 6.06 8.283 "Dataset is not sorted" SAS Error fixed by Z6062141.
SPIN 8.158 SPIN library fills when MVS/ESA replaces MVS/XA.
SPIN 8.172 SPIN library fills when MVS/ESA replaces MVS/XA.
SPUNJOBS 8.258 New PDB.SPUNJOBS dataset for SPIN reporting.
TRND72 8.143 Critical error, but only in PreRelease 8.3
TRNDDB2A 8.276 TRENDing for DB2ACCT into MXG Trend database.
TRNDDB2S 8.279 TRENDing for DB2STAT0 and DB2STAT1.
TRNDRMFI 8.143 Critical error, but only in PreRelease 8.3.
UTILGETM 8.206 %MACRO on FILE statement CPU loop in SAS 6.06.
VMAC110 8.065 Support for new CICS 3.1.1 major changes.
VMAC1415 8.017 New hiperbatch counts added to SMF type 1415.
VMAC1415 8.137 Hiperbatch values non-zero when they should be zero.
VMAC23 8.208 SMF writer memory usage added (OY27449).
VMAC28 8.111 INPUT function error in NPM subtype 82.
VMAC28 8.148 Support for NPM Release 4 (NPM 1.4), SMF Type 28.
VMAC30 8.081 Support for APAR adding DDCONS() option.
VMAC30 8.082 Support for APAR adding PROCSTEP to type 30s.
VMAC30 8.208 NOT CATLG 2 or 7 now added (APAR OY24857) to 30s.
VMAC37 8.022 Variable KEEP, FORMATs.
VMAC39 8.022 TYPE39EL conditionally created. ZDATE kept.
VMAC39 8.245 Support for NETMASTER V2.1.0 subtype 255.
VMAC41 8.015 New VLF counts in new subtype 3 SMF type 41.
VMAC42 8.136 STOPOVER on subtype 3 due to IBM error.
VMAC57 8.184 STOPOVER on type 57 (MVS 4.1 and MXG 8.5 only).
VMAC6 8.057 STOPOVER due to invalid external writer record.
VMAC60 8.128 STOPOVER on SMS NVR segment in type 60.
VMAC6156 8.027 STOPOVER error with ICF catalog record section.
VMAC6156 8.039 TYPE6156 VOLSER may be wrong for GDGs.
VMAC6156 8.214 "Invalid Third Argument to Function SUBSTR."
VMAC64 8.134 ACBMACRF fields individually decoded into variables.
VMAC64 8.219 TYPE64 hiperbatch variables missing.
VMAC64 8.234A VSAM Hiperbatch counters corrected.
VMAC7072 8.066 Support for new "SRCL" field in RMF Product section.
VMAC7072 8.187 Support for new Hitachi processors with MLPF.
VMAC7072 8.233 "Invalid data for MSOCOEFF..." correction.
VMAC7072 8.250 Support for PR/SM "overhead" measure APAR OY36668.
VMAC76 8.254 Support for OPPSI in SYSPLEX is traceable.
VMAC78 8.049 TYPE78CF only output if CHPID is online.
VMAC78 8.132 STOPOVER on type 78 subtype 3 with ES/9000 CPUs.
VMAC79 8.012 STOPOVER correction, support validation.
VMAC79 8.055 Formats and units corrections.
VMACACF2 8.002 ACF2 SMF record caused STOPOVER.
VMACACF2 8.090 Further validation of ACF2 SMF record.
VMACARB 8.190A Support for Arbiter Version 2.1.1 SMF records.
VMACCIMS 8.064 Support for IMF 2.6 (for IMS 3.1).
VMACCMF 8.247 Support for Boole & Babbage CMF SMF record 240.
VMACCRAY 8.044 Support for CRAY COS operating system
VMACDB2 8.102 Distributed DB2 header added to DB2ACCT.
VMACDB2 8.225 Support for Landmark's The Monitor for DB2.
VMACDCOL 8.130 DCOLLECT enhancement for all seven records.
VMACDCOL 8.210 DCOLLECT migration/backup tape dates correction.
VMACDCOL 8.252 Support for DCOLLECT APAR OY37378.
VMACDCOL 8.074 Support for SMS DCOLLECT data records.
VMACDMON 8.003 Uninitialized variable in ANALDMON caused.
VMACDMON 8.236 Support for LEGENT ASTEX replacement for DASDMON.
VMACEPMV 8.217 Support for Candle's EPILOG for MVS SMF Type 180.
VMACHSM 8.138 Preliminary support for HSM User SMF records.
VMACIDMS 8.005 IDMS SMF record variables format incorrect.
VMACIMS 8.006 IMS crashes required duplicate DTOKEN protection.
VMACIMS 8.098 Support for IMS/ESA 3.1 log records.
VMACIMS 8.118 IMS Cold start support and logic changes.
VMACIMS 8.119 Correction of IMS Input Queue time.
VMACIMS 8.176 IMS 3.1 DBCTL Thread Transactions Deleted.
VMACIMS 8.256 Support for IMS Wait-for-Input from IMS log.
VMACMDF 8.091 Amdahl's MDFTRACH SMF records corrected.
VMACMEMO 8.227 Support for MEMO European Electronic Mail SMF record.
VMACMON8 8.161 Support for Landmark's Monitor for CICS Version 8.0
VMACMONI 8.036 CREATIME in MONITASK may have wrong date.
VMACMPT 8.173 Support for Amdahl's MDF Performance Tool
VMACNSPY 8.010 NETSPY 3.2 support was incomplete.
VMACNSPY 8.043 Netspy 3.1 STOPOVER.
VMACNSPY 8.265 Support for NETSPY Release 4.0.
VMACORAC 8.080 Support for Oracle SMF record.
VMACROSC 8.028 ROSCOAUD contained zero observations always.
VMACSASU 8.157 SAS User Record changed under SAS 6.06.
VMACSESA 8.228 Support for Volvo's SESAME VTAM Monitor.
VMACSMF 8.013 DB2 read from GTF. Minor.
VMACSPMS 8.149 Support for Amdahl's SPMS SMF (Cache DASD CU).
VMACSTC 8.092 STC 4400 Silo SMF record new subtype.
VMACSTC 8.194 STC 4400 Silo SMF record new subtype STOPOVER!
VMACSYNC 8.020 Invalid CPUTCBTM value detected.
VMACSYNC 8.056 SIRECFM,SORECFM contain invalid data value.
VMACSYNC 8.123 Error (only in PreRelease 8.2) in TYPESYNC data.
VMACSYNC 8.211 SYNCSORT EW2903 detects SAS invoked Sort.
VMACSYNC 8.253 Support for SYNCSORT SCZ 33038 (Hiperspace stats).
VMACTMNT 8.033 Minor. Formats for DEVFROM/DEVTO.
VMACTMVS 8.173 Protection for TMON/MVS Spanned Records
VMACTPNS 8.269 Support for TPNS log.
VMACTPX 8.016 No observations in TPXINTRV.
VMACTSOM 8.007 Missing STRTTIME in TSOMCMND.
VMACTSOM 8.104 Invalid READTIME due to CA7 in TSO/MON record.
VMACTSOM 8.262 Support for LEGENT TSO/MON Release 5.3.0.
VMACVMON 8.037 Divide by zero.
VMACVMON 8.045 24APR90 became 02OCT89 when 202 day clock wrapped.
VMACVMON 8.106 VM Start Time off by 43 minutes on Aug 4, 1990.
VMACVMXA 8.004 OMEGAMON/VM creates invalid VM/XA VB records.
VMACVMXA 8.099 Many VM/XA PTFs altered Monitor records.
VMACVMXP 8.041 Minor EXPLORE/VM processing changes.
VMACVPD 8.234 Support for NETVIEW's VPD aka NAM type 37 SMF data.
VMACVVDS 8.073 Validation of VVDS record created by ASMVVDS.
VMACWSF 8.100 Support for WSF archive product SMF.
VMACX37 8.024 STOPX37, minor.
VMACZRB 8.054 RMF 4.1.1 caused STOPOVER.
VMACZRB 8.079 Further validation of RMF III VSAM data.
VMACZRB 8.156 Further validation and reports.
VMXGDOWN 8.273 Download to PC all datasets in a SAS library.
VMXGSUM 8.021 Missing variable initialization protection.
VMXGVTOC 8.018 OFFSET4E and SMS variables added.
VMXGVTOC 8.032 Minor. RECFM should be $4.
VMXGVTOC 8.075 Did not capture free space at beginning of volume.
VMXGVTOF 8.193 Build VMXGVTOC datasets from ASMVTOC records.
VMXGVTOR 8.009 Incorrect on 7.7, changes not propagated.
XMAC7072 8.014 ZDATE not kept in TYPE70PR and TYPE72MN
ZZZZZZZZ 8.011 Final member of MXG Library is named.
Inverse chronological list of all Changes:
NEXTCHANGE: Version 8 72
--- Changes 8.305 thru 8.286 were added after MXG 8.8 was shipped ---
Change 08.305 About 90 of the 32,000+ MXG variables had no labels, some
DOC obsecure datetime variables were not formatted, and some
Apr 30, 1991 variables were length 8 when they should have been only
4 bytes long, as discovered in the MXG QA jobstreams. All
of these that could be corrected easily were!
Change 08.304 Type 79 support (RMF Monitor II) has now been extended
VMAC79 backwards to include RMF 3.5.1, and code was cleaned up
Apr 29, 1991 with this significant user contribution.
Thanks to Gordon Keehn, Fidelity Mutual Life Insurance Company, USA.
Change 08.303 IMS Log processing temporary variable OENQTO should have
TYPEIMS been spelled OENQO in line 107900.
Apr 28, 1991
Change 08.302 VM/ESA variable CHANBYTM was stored 8 bytes, but can be
VMACVMXA stored in only 4 bytes. Add CHANBYTM before DURATM in
Apr 28, 1991 the LENGTH statement at the end of line 060650.
Change 08.301 The New DB2 Trending members run fine the first week, but
TRNDDB2S in subsequent runs, the three shifts in prior weeks data
Apr 28, 1991 are summarized into a single observation for the entire
week (and SHIFT appears as Weekend). The recalculation
of SHIFT in trending should have only been applied to the
new PDB data, but bad logic caused the corruption.
This correction is for the DB2 Statistics trending member
TRNDDB2S. See Change 8.300 for DB2 Account trending.
1. The INCODE= argument at 005200:
INCODE = 005200
IF INWEEK THEN NUMINTVL = 1; 005300
LABEL NUMINTVL='NUMBER OF*STATISTICS*INTERVALS'; 005400
OUTPUT MXGSUM1; 005500
DATA MXGSUM1 005600
TIMES 005700
(KEEP=SYSTEM SHIFT QWHSSSID QWHSSTCK MINTIME MAXTIME); 005800
SET MXGSUM1; 005900
IF DURATM GT 0 THEN MINTIME=QWHSSTCK-DURATM; 006000
ELSE MINTIME=.; 006100
MAXTIME=QWHSSTCK; 006200
%VMXGDUR(DATETIME=QWHSSTCK,INTERVAL=WEEK,NEWSHIFT=Y); 006300
QWHSSTCK=DATETIME; 006400
OUTPUT MXGSUM1; 006500
OUTPUT TIMES;, 006600
Must be changed to read
INCODE = 005200
IF INWEEK THEN DO; 005300
NUMINTVL = 1; 005310
IF DURATM GT 0 THEN MINTIME=QWHSSTCK-DURATM; 005320
ELSE MINTIME=.; 005330
MAXTIME=QWHSSTCK; 005340
%VMXGDUR(DATETIME=QWHSSTCK,INTERVAL=WEEK,NEWSHIFT=Y); 005350
QWHSSTCK=DATETIME; 005360
END; 005370
LABEL NUMINTVL='NUMBER OF*STATISTICS*INTERVALS'; 005400
OUTPUT MXGSUM1; 005500
DATA MXGSUM1 005600
TIMES 005700
(KEEP=SYSTEM SHIFT QWHSSSID QWHSSTCK MINTIME MAXTIME); 005800
SET MXGSUM1; 005900
QWHSSTCK=DATETIME; 006000
OUTPUT MXGSUM1; 006500
OUTPUT TIMES;, 006600
2. The INCODE= argument at 012300:
INCODE = 012300
IF INWEEK THEN DO; 012400
IF QXMSMIAP=. THEN QXMSMIAP=.; 012500
IF QXNSMIAP=. THEN QXNSMIAP=.; 012600
IF QXNSMIAP=. AND QXMSMIAP GT 0 THEN QXNSMIAP=QXMSMIAP; 012700
END; 012800
OUTPUT MXGSUM1; 012900
DATA MXGSUM1 013000
TIMES 013100
(KEEP=SYSTEM SHIFT QWHSSSID QWHSSTCK MINTIME MAXTIME); 013200
SET MXGSUM1; 013300
IF DURATM GT 0 THEN MINTIME=QWHSSTCK-DURATM; 013400
ELSE MINTIME=.; 013500
MAXTIME=QWHSSTCK; 013600
%VMXGDUR(DATETIME=QWHSSTCK,INTERVAL=WEEK,NEWSHIFT=Y); 013700
QWHSSTCK=DATETIME; 013800
OUTPUT MXGSUM1; 013900
OUTPUT TIMES;, 014000
Must be changed to read
INCODE = 012300
IF INWEEK THEN DO; 012400
IF QXMSMIAP=. THEN QXMSMIAP=.; 012500
IF QXNSMIAP=. THEN QXNSMIAP=.; 012600
IF QXNSMIAP=. AND QXMSMIAP GT 0 THEN QXNSMIAP=QXMSMIAP; 012700
IF DURATM GT 0 THEN MINTIME=QWHSSTCK-DURATM; 012710
ELSE MINTIME=.; 012720
MAXTIME=QWHSSTCK; 012730
%VMXGDUR(DATETIME=QWHSSTCK,INTERVAL=WEEK,NEWSHIFT=Y); 012740
QWHSSTCK=DATETIME; 012750
END; 012800
OUTPUT MXGSUM1; 012900
DATA MXGSUM1 013000
TIMES 013100
(KEEP=SYSTEM SHIFT QWHSSSID QWHSSTCK MINTIME MAXTIME); 013200
SET MXGSUM1; 013300
DATETIME=QWHSSTCK; 013800
OUTPUT MXGSUM1; 013900
OUTPUT TIMES;, 014000
Change 08.300 The New DB2 Account Trending has the same problem cited
TRNDDB2A for the DB2 Statistics Trending discussed above in the
Apr 28, 1991 Change 8.301.
This correction involves also requires two parts:
1. The two lines, 012900-013000, now reading:
MINTIME=QWACBSC; 012900
MAXTIME=QWACESC; 013000
Must be MOVEd to after 004900 (MOVE, not COPY!).
2. Then, the two lines, 019800-019000, now reading:
%VMXGDUR(DATETIME=QWACESC,INTERVAL=WEEK,NEWSHIFT=Y); 019800
QWACESC=DATETIME; 019900
Must be MOVEd to after the lines just moved above.
The end result of these two moves will be:
IF INWEEK THEN DO; 004900
MINTIME=QWACBSC; 004910
MAXTIME=QWACESC; 004920
%VMXGDUR(DATETIME=QWACESC,INTERVAL=WEEK,NEWSHIFT=Y); 004930
QWACESC=DATETIME; 004940
IF QXMSMIAP = . THEN QXMSMIAP = .; 005000
Change 08.299 A "Variable Not Found" condition occurs with ANALDB2R if
ANALDB2R the Accounting Trace Long report was requested by itself.
Apr 28, 1991 (If any other report was also requested, this error does
not occur). Line 021820, which now reads:
TIMES (KEEP=&SORT1 &SORT2 &SORT3 MINTIME MAXTIME);
was replaced by these 6 lines:
%IF &PMACC02 EQ YES %THEN %DO;
TIMES (KEEP=&SORT1 &SORT2 &SORT3 MINTIME MAXTIME);
%END;
%ELSE %DO;
TIMES (KEEP=DB2 MINTIME MAXTIME);
%END;
Thanks to Ron Roberts, The Equitable Life Assurance Society, USA.
Change 08.298 Fujitsu's AIM database manager (CICS-like) SMF records
VMACAIM2 were in error. The FILLER $CHAR2. in VMACAIM2 line 117
VMACAIM3 was deleted. In VMACAIM3, NUMSCHMA is PIB2, not PIB4,
Apr 28, 1991 and the DO loop in line 65 should be 1 to NUMSCHMA. These
changes were received long ago and should have been in
earlier versions. Thanks for the contributor; Bill has
provided them locally to Fujitsu sites down under!
Thanks to Bill Gibson, SAS Institute, AUSTRALIA.
Change 08.297 Support for Fujitsu's FACOM operating system now includes
TYPEPDL both MSP and FSP data from PDL reports from PDA records.
TESTFACO Former "X-rated" member XPDLPDA is now renamed TYPEPDL,
JCLTEST and first-time-logic added for history datasets. The MXG
JCLTEST6 test and cross reference jobstreams now separately test
JCLUXREF all FACOM support in step TESTFACO, so that all 25 of the
JCLUXRE6 RTYPExx datasets and histor datasets created by TYPEPDL
Apr 19, 1991 are documented in DOCVER. The coding changes that added
FSP support were a significant user contribution, and
also added decoding of several additional PDL reports.
Thanks to Ian Heaney, M.L.C., AUSTRALIA.
Change 08.296 VM/XA processing requires more work space that it should
VMACVMXA because the PROC DATASETS to delete VXUSEINT and VXACTINT
Apr 19, 1991 was commented out during testing. Remove the comments in
line 798400. Also, variable RDEVOFFL was not kept because
it was misspelled as RDEFOFFL in the KEEP= list.
Thanks to Jay Cicardo, Southwestern Bell, USA.
Change 08.295 SAS datasets will be destroyed/corrupted by CASORT 6.6
CASORT 6.6 if its ATTRLS Option (system wide, set when CASORT was
Apr 18, 1991 installed) was specified ATTRLS=YES. Instead, you MUST
have ATTRLS=NO. With ATTRLS=YES, CASORT will RLSE sort
work space after each invoked SORT, which somehow causes
SAS to think all records were deleted by NODUP, and the
output dataset built by the PROC SORT contains either
zero or one observation! If there is one observation,
all of its numeric variables are zero or missing, which
happened with RMFINTRV, and the garbaged dates/times
put messages on the SAS log, but then caused the TREND
database to be overwritten with only one observation!
CA says the problem is known to affect ANY invoked sort,
not just SAS invoked sorts. SAS tracking 180027 is open,
to determine why SAS built the corrupted 1-observation
data set, and I will investigate how I can make the trend
logic more robust, but you MUST specify ATTRLS=NO to fix
the real problem with CASORT 6.6.
Thanks to Arnold Ruterbories, Standard Insurance Company, USA.
Change 08.294 Additional SAS 6.06 error conditions have been reported.
SAS 6.06 a.VMXGVTOC will fail "VARIABLE VOLSER NOT FOUND", if you
Apr 18, 1991 installed SAS ZAPs Z6061834 or Z6062315, due to an error
introduced by those zaps (the "autovariable" VOLSER was
lost when those zaps were installed). SAS ZAP Z6062674
now exists to correct their error and is required. It is
not on the April SAS Notes tape, but can be downloaded.
b.SAS will ABEND with an 0C4 in SMS sites, if the datasets
in the CONFIG DD concatenation are SMS-managed datasets,
if the CONFIG= JCL parameter is used. (If you used the
prior MXG technique of actually overriding the CONFIG DD,
this abend does not occur, but then you must be careful
to order the JCL override, thus the CONFIG= parameter was
recommended instead of overriding the CONFIG DD!) The SAS
error is fixed by ZAP Z6062264, which is required if your
site has SMS-managed datasets for SAS and or MXG.
Change 08.293 -IBM's Cache DASD RMF Reporter "CRR" Product's SMF records
ANALCACH status bits were changed (don't know when!) and count of
FORMATS sequential-detected sequential read requests was added.
VMACACHE Variables have been dropped from CACHE90. Flag variables
Apr 18, 1991 (CSCS1-CSCS8,CSNVSS1-CSNVSS8, CSDP,CSCD,CSFF,CSFD,CSPD,
CSSD,CSFC,CSPP) are replaced by format-decoded variables,
and the caching/fastwrite/pinning/etc. status variables
from the CSVOL segment (which apply only to that CSVOL,
and not to the VOLUME being reported) are not kept. IBM's
3990 Storage Control Reference, GA32-0099-3, pp 171-177,
Chapter 4, Command Descriptions, describes the statistics
captured much better than the CRR manual (SH20-6295-4).
CACHE90 variable FWDC, the count of DASD fast write ops
that were forced to access DASD directly (because the
nonvolatile storage was insufficient), may be important
in recognizing this performance degradation.
-The Cache analysis program ANALCACH was revised to now
CACHE90 (instead of the CACHETY data from 3880's) along
with RMF TYPE74 data for sample reports.
Thanks to Victor Heiner, Northwest Airlines, USA.
Thanks to Alfred Holtz, Dun and Bradstreet, USA.
Change 08.292 Boole & Babbage CICS Manager product causes MXG messages
VMAC110 "Unexpected Statistics Subtype" with STID=200 to 210, due
Apr 16, 1991 to that product's pseudo type 110 statistics records. The
additional records will be supported in the future.
Thanks to Paul Dean, IBM Hursley, ENGLAND.
Change 08.291 Variables EXCPTOTL and IOTMTOTL should have been in the
ASUMJOBS KEEP= list for dataset BATCHJOB (added by Change 8.230
Apr 16, 1991 for detect duplicate job hold enhancement).
Thanks to Elliot Weitzman, Oryx Energy Company, USA.
Change 08.290 MVS Account Fields with length=0 create MXG error message
IMACACCT "***ERROR.IMACACCT.ACCOUNT FIELD n LENGTH WRONG", and any
Apr 16, 1991 account fields after the zero length field are skipped.
If the "n" in the message is greater than the number of
Account Fields you are KEEPing, there is no impact on the
datasets built by MXG. The enhancement in Change 8.267
(to prevent STOPOVER if account length were wrong) failed
to allow for a zero length field. The nine lines that
now read "ELSE DO;" must be change to read:
(line number)
ELSE IF LENACCT1 GT 0 THEN DO; 012300
ELSE IF LENACCT2 GT 0 THEN DO; 014000
ELSE IF LENACCT3 GT 0 THEN DO; 015700
ELSE IF LENACCT4 GT 0 THEN DO; 017400
ELSE IF LENACCT5 GT 0 THEN DO; 019100
ELSE IF LENACCT6 GT 0 THEN DO; 020800
ELSE IF LENACCT7 GT 0 THEN DO; 022500
ELSE IF LENACCT8 GT 0 THEN DO; 024200
ELSE IF LENACCT9 GT 0 THEN DO; 025900
This error occurs ONLY if your IMACACCT was tailored from
MXG version 8.8.
Thanks to Mike Hoevenaars, Toyota Canada, CANADA.
Change 08.289 ACF2 Release 5.2 added four variables (ACPMFCPM,ACPMFCJN,
VMACACF2 ACPMFCJI, and ACPMFCLI to the ACF2PR dataset & variables
Apr 16, 1991 ACVMFLRT, ACFMFTRT, and ACVMFTRS to ACF2VR dataset.
Thanks to Dave Greene, Kwasha Lipton, USA.
Change 08.288 Format MGSYNDB for SYNCSORT value 2 should have formatted
FORMATS to 2:3390 instead of the (now nonexistent) 2:3330 device,
Apr 16, 1991 and values 16 and 24 were added to ACF2 formats MGACFDA
and MGACFDB respectively.
Thanks to Dave Greene, Kwasha Lipton, USA.
Change 08.287 Member VMACEPIL on the original MXG 8.8 tape was wrong.
TESTOTHR Instead of the complete revision of support for Candle's
VMACEPIL EPILOG/CICS, VMACEPIL contained a copy of member CHANGES!
Apr 16, 1991 This error also caused JCLTEST step TESTOTHR to fail.
This change simply puts back VMACEPIL in VMACEPIL!
Thanks to Rex Pommier, St. Lukes Hospital Fargo, USA.
Change 08.286 IEBUPDTE unload of MXG 8.8 ends with condition code four,
V88-tape prints "IEB823I SYSIN HAS NO RECORDS for AS400PDS", and
Apr 11, 1991 MXG.SOURCLIB contains 1394 members instead of the stated
1367 members, but this warning has no real impact on the
MXG.SOURCLIB data set. The warning occurs because member
AS400PDS itself was an IEBUPDTE input for a 28-member PDS
with preliminary support for AS400 data. Your unload saw
those "./" statements and created the 28 members starting
with @@@....., AS400..., ICEGENER, and QAPM.... directly
in your MXG.SOURCLIB, and then there were no lines in the
member AS400PDS, causing the warning! I had intended to
change the "./" to "xy" in AS400PDS to avoid this warning
but failed to do so. Sorry for all those phone calls and
faxes that would have been avoided by better testing.
Thanks to Ken Thomas, Maryland Casualty Company, USA.
--Changes thru 8.285 are included in MXG Version 8.8 dated Apr 8, 1991-
Change 08.285 A surprising discovery by looking at DCOLLECT data. DASD
VMACDCOL capacity stated by IBM (eg, 630MB for a 3380 volume) is
Apr 4, 1991 NOT 630 Megabytes, but instead is 630 "Million bytes"!
A 3380 (47476*15*885 = 630,243,900 bytes) actually stores
Dostları ilə paylaş: |