* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
BUIL3005 29.106 JES3 PDB.JOBS variable JOBCLAS8 has after change. BUILDPDB 29.068 MXG 28.28-29.02. ABEND=JCL obs missing in PDB.JOBS. DB2ACCT 29.111 DB2 CICS TRAN name could be wrong, now from QWHCCV. DB2ACCTP 29.053 Doc. QWACxxxx variables in DB2ACCTP always missing. EXITCICS 29.064 Rare (one-site) error in INFILE exit corrected. GRAFWRKX 29.185 Workload RMFINTRV graph's update uses new workloads. IMACICRD 29.302 Comment within comment block if default used. JCLSPLIT 29.241 Example to split SMF had 102 records copied twice. MONTHBLD 29.008 MXGNOBY default to eliminate NOTSORTED exposure. MONTHBLD 29.017 SERIOUS ERROR CORRECTED: last day's PDB skipped. MONTHxxx 29.052 SAS 9.1.3 Only. %QCMPRES needed versus %CMPRES. MXGSASxx 29.265 MXGTEMP temporary DDNAME/FILENAME added to MXG JCL. RMFINTRV 29.005 Doc: INTERVAL=QTRHOUR became default in 28.01. RMFINTRV 29.194 Stats on Page Dataset Slot Usage added to RMFINTRV. RMFINTRV 29.305 INTERVAL=SHIFT generated warnings & incorrect output. SAS V9.3 29.159 Support for SAS Version 9.3 - SAS Hot Fix SN43828. SMFSRCH 29.236 SMFSRCH, search SMF records for text, print all obs. TYPE0 29.032 PDB.IPLS, now, DOES always report a SYSTEM IPL. TYPE102 29.125 DB2 SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED error. TYPE102 29.235 IFCID=22 in Change 28.234 wrong in DB2 V9. TYPE105 29.100 Support for GDPS Global Mirror V3R8 SMF 105 record. TYPE110 29.076 CICS CPUTM exceeds ELAPSTM, zAAP/zIIP Equivalent time TYPE110 29.094 1st MXG 29.03 ONLY. CICSTRAN CPUTM plus fields WRONG. TYPE110 29.097 INPUT EXCEEDED 110-2 MNSEGLC=5 with DPL segment TYPE110 29.135 Support for CICS/TS 4.2 was in 29.03. TYPE110 29.155 CICS/TS 4.2 Statistics variables overlooked, added. TYPE110 29.221 CICS Statistics datasets CICDB2GL,CICSMDSA, corrected TYPE110 29.293 Support for CICS Statistics STID=143 and 144. TYPE111 29.001 Support for IPIC creates obs in TY111CXI. TYPE111 29.124 Variables CTGIAREQ/CTGLALRQ revised keeps. TYPE111 29.153 UNDECODED CTGRECID message, possible CPU loop. TYPE113 29.060 z196 Est Finite CPI, Est SCPL1m calcs revised. TYPE113 29.080 New variables and label revisions. TYPE113 29.176 Support for APAR OA36816, SMF 113 HIS DATALOSS parm. TYPE115 29.015 Support for MQ Version 7 compression statistics. TYPE115 29.057 Support for Websphere for z/OS MQ Version 7.0.1. TYPE115 29.161 MXG 29.03-MXG 29.05 dataset MQMCFMGR was wrong. TYPE116 29.057 Support for Websphere for z/OS MQ Version 7.0.1. TYPE119 29.215 Variables T119STCK/TISSTCK/TIESTCH were still GMT. TYPE120 29.081 Support for User Field in SMF 120 Subtype 9 record. TYPE120 29.136 Support for WebSphere WAS 8.0 (COMPATIBLE). TYPE120 29.240 Length of Character Variable SMF1209FH can't change. TYPE120 29.272 SM1209CI and SM1209CX can be negative. TYPE1415 29.226 False ERROR.TYPE1415.DEFECTIVE.EXTENDED... log msg. TYPE16 29.232 DFSORT variables ICEMNVLX, ICEMNVLY, ICEMNVLZ wrong? TYPE16 29.264 Support for DFSORT z/OS 1.13 COMPAT new variables. TYPE19 29.183 Variables SMF19TRK and SMF19TRM were wrong. TYPE23 29.177 Support for APAR OA35175, logstream stats in SMF 23. TYPE26J2 29.024 Cosmetic: INREASON NOT DECODED messages corrected. TYPE30 29.025 Small negative CPUUNITS now set to zero. TYPE30 29.034 Invalid data for SMF30RGT is true, circumvented. TYPE30 29.058 Variable CPUCEPTM always now set to a missing value. TYPE30 29.174 Support for APAR OA34895, EXCP/IOTM Missed, SMF Lock. TYPE30 29.175 Support for APAR OA35617, SMF30CRM VELOCITY MNGED? TYPE57 29.173 Support for APAR OA36966, JES3 expanded NJEJOBNO. TYPE70 29.127 Support for z/OS 1.12 VMGUEST option, CPU Time in 70. TYPE7072 29.077 z/OS under z/VM: MXG messages, nonexistent RMF data. TYPE7072 29.152 VMSYSTEM='Y' RMF records validated, and revised. TYPE7072 29.220 Support for z/OS 1.13 (REQUIRES MXG 29.03 or later). TYPE70PR 29.098 Counts ICFCPUS/IFLCPUS/IFACPUS/ZIPCPUS too high. TYPE70x 29.239 Variable SHIFT (used as "ZONE") added to all RMF. TYPE78PA 29.214 Values in TYPE78PA ending with TOTL could be wrong. TYPE80A 29.223 New TOKENIDs starting with NOxxxx (NOCPUTIMEMAX, etc) TYPE845 29.212 Invalid JES3 JMF SMF 84 Subtype 1 Segmented Records. TYPE85 29.093 INPUT STATEMENT EXCEEDED st 79, z/OS 1.12. TYPE89 29.002 Support for APAR OA31615, zIIP/zAAP times added. TYPE89 29.178 Variable CECSER in 89 now contains only 4 positions. TYPE90A 29.142 Enclave variables decoded in TYPE9030 dataset. TYPEADAB 29.189 Support for Software AG's ADABAS SMF user record. TYPEAXWY 29.231 Support for Axway CFT/ESA (Cross File Transfer) SMF. TYPEBBMQ 29.056 Support for MainView MQ (MVMQ) Version 4.4. TYPEBETA 29.059 Support for Beta 93 Version 4.2 subtypes 25/50. TYPEBETA 29.233 Support for BETA93 Version 4.1.0 subtype 25 changes. TYPEBVIR 29.006 Variables DVRTBV01-32 incorrectly formatted. TYPECFS 29.186 Support for InfoSphere Classic Federation Server SMF. TYPECIMS 29.033 Support for IMF Version 4.5 is in place. TYPEDB2 29.031 DB2 V9.2 only, most QBGxxx variables DB2GBPST wrong. TYPEDB2 29.121 QWHADSGN/QWHAHAMN were sometimes blank. TYPEDB2 29.128 DB2 INVALID DISTRIUTED HEADER message corrected. TYPEDB2 29.131 DB2PARTY added to DB2ACCTP, Rollup impact documented. TYPEDB2 29.140 New LUUVTIME instead of QWACBSC for start time. TYPEDB2 29.209 DB2 V10 ID=100 ST=1 INVALID HEADER. TYPEDB2 29.213 Support for DB2 V10 IFCID 225 Subtype4 INCOMPATIBLE. TYPEDB2 29.225 INVALID DB2 V10 QMDA segment for QMDAPTYP='JCC'. TYPEDCOL 29.296 DCOLLECT support updated to execute on ASCII. TYPEDM 29.158 NDM-CDI Version 5 new fields supported. TYPEENDV 29.012 Support for Endeavor Version 14 (INCOMPATIBLE). TYPEFERT 29.247 Support for ZEN FERRET V2.3 (INCOMPATIBLE). TYPEIDMS 29.156 Support for IDMS/R Performance Monitor Version 18. TYPEIMS 29.307 Support for IMS Version 12: Adds ZIIP/ZAAP CPU times. TYPEIMSA 29.110 the exit _IMSTRN invocation was accidentally removed. TYPEIMST 29.144 IMS Transaction Detail in new IMS56FA dataset!! TYPEIMST 29.162 Validation of TYPEIMST, many changes for IMS56FA. TYPEIMST 29.230 Further updates to IMS56FA transaction processing. TYPEITRV 29.223 Support for APAR OA37114, ITRF (OMEGAMON IMS V420) TYPEMPLX 29.247 Support for ZEN IMPLEX V5.1 (COMPATIBLE) TYPENDM 29.010 NDMPRCNM/NDMPRCNO/NDMSTEP now kept where they exist TYPENDM 29.042 Support for NDM-CDI Version 5 records (COMPATIBLE). TYPENDM 29.295 NDM/Connect-Direct V5.0 added jobname/jctjobid. TYPENDM 29.301 Old Version 4.7 "PS" record INPUT STATEMENT EXCEEDED. TYPENTSM 29.075 Support for 62 new objects and 1425 new NT metrics. TYPEPOC 29.219 Support for Tivoli Workload Schedulr Ver 8.3 INCOMPAT TYPEPOEX 29.134 Support for Informatica's POWER EXCHANGE SMF record. TYPEQACS 29.078 Support for OS/400, AS/400 Version 7.1 (INCOMPATIBLE) TYPEQACS 29.208 Support for IBM i-series (AS400), more than 32 CPUs. TYPERACF 29.067 RACF UNLOAD dataset RACF0270 UID limit variables. TYPERMFV 29.013 CPCGRPLM and LCPUPOLR variables were wrong. TYPERMFV 29.297 Continued RMF III enhancements. TYPERMFV 29.300 Wrong ASMRMFV in first 29.29, VMACRMFV updated. TYPESVIE 29.273 Support for SYSVIEW subtypes 34 and 35. TYPETIMS 29.123 Support for TMON/IMS Version 3.0 (INCOMPATIBLE). TYPETLMS 29.269 Support for CA TLMS tape library 2003 record changes. TYPETMNT 29.248 INVALID ARGUMENT TO SUBSTR IN SYSLOG IEC205I message TYPETMO2 29.244 Support for TMON/CICS V3.3 (mostly COMPATIBLE) TCE. TYPETMS5 29.274 CA-1 TMS Extended Format TMC records have no impact. TYPETMS5 29.304 USER ABEND 1234 can be bypassed for TMSCLEAN input. TYPETPMX 29.071 Support for Throughput Manager subtype 10 and 16. TYPETPMX 29.211 Support for Throughput Manager APAR TMT6214, st=16. TYPETPMX 29.229 TPMCA7JN, TPMPI, and TPMDUEOT may be wrong. TYPEVMXA 29.014 z/VM MONWRITE "exit" at EOF to detect ftp failure. TYPEVMXA 29.026 Support for zVM APAR VM64794 (COMPATIBLE). TYPEVMXA 29.092 z/VM new PDB.VXINTUSR sums all engines for each VM. TYPEVMXA 29.129 MXGERROR DM 5 RC 10 UNDECODED PRCAPMCT due to IBM. TYPEVMXA 29.133 z/VM LPARNAME, LPNUMBER kept in PDB.VMXAINTV. TYPEVMXA 29.163 z/VM Crypto Record (5,10) with PRCAPMCT=6 error. TYPEVMXA 29.172 Support for APAR VM64961, SMF 113 in z/VM MONWRITE!! TYPEVMXA 29.207 z/VM MONWRITE Broken Control Rec if 2.14 (SCALL) rec. TYPEXAM 29.126 XAM variables in VXSYTEP2 were not all input/kept. TYPEXAM 29.294 Support for VNDNIC, LPARNW, USVCPU segments. TYPEZOSA 29.247 Support for new ZEN OSA MONITOR V1.3 SMF records. TYPEaaaa 29.238 All USER SMF have MACRO _IDaaaa nnn as SMF record id. TYPSXAM 29.249 TYPSXAM didn't sort all XMdddddd datasets to the PDB. UTILARCH 29.137 New UTILARCH archives data (like Outlook archive). UTILVREF 29.075 MXG now creates DATASET names up to 32 characters. VMAC102 29.242 On ASCII COMPRESS turned off, QW0145TX maybe trashed. VMAC30 29.281 CPUTASKALLTM and PCTTASKTIME added SMFINTRV/TYPE30_V. VMACDB2H 29.037 DB2 V9.1 false "INVALID DISTRIBUTED HEADER" message. VMACSMF 29.079 MXG will ABEND if SMFTIME is invalid. VMACSMF 29.290 USER ABEND 69 due to invalid SMFTIME now bypassed. VMXGGETM 29.224 Enhancements to select records with LOOKFOR=text. VMXGMPDB 29.292 Support for execution under unix. VMXGPPDS 29.298 Compare contents of multiple PDS/PDSE libraries. VMXGPRNT 29.250 INSTREAM replaces TMPPRNT.SAS for ASCII restrictions. VMXGSRCH 29.103 RESULTS=FINDVAR finds all datasets with a variable. VMXGSUM 29.054 Macro variable DSETEXST redefined. VMXGSUM 29.154 AUTOCALL %macro's %CMPRES/%QCMPRES removed. VSETMNTH 29.041 POSSIBLE LOSS OF MONday DATA in FEBRUARY MONTHLY PDB. WEEKBLD 29.008 MXGNOBY default to eliminate NOTSORTED exposure. See member CHANGESS for all changes ever made to MXG Software. Inverse chronological list of all Changes:
VMACIMS IBM changes were COMPATIBLY made, used RESERVED fields, Jan 21, 2012 and those CPU times were added by APAR PM36273. These new variables are now created in IMS01/IMS01M: MSGOD62I='APPC*DEST*TYPE' MSGOD62A='APPC*DETT*ADDR' MSGIHSQN='SUBPOOL*HSQN*NM' MSGFMTNM='MFSMODNAME' MSGEWTKN='WLM*TOKEN TO*C2*CORRELATOR' These new variables are now created in IMS07 and IMS0708: DLRXICAL='ICAL*CALLS' DLRXDGUR='DATABASE*GUR*CALLS' DLRFLAG4='DLRFLAG4' DLRAZAAP='ZAAP*ZIIP*CPU*TIME' This new variable is now created in IMS07 and IMS0708: LINTSUB2='IMS08*SUBTYPE*ADDITIONAL' These two variables are now created in IMS56FA: DLRGUR ='DL/I*GUR*CALLS' TPEZAAP ='ZAAP*ZIIP*CPU*TIME' Thanks to Paul Volpi, UHC, USA. Thanks to Jerome Bachmeier,, UHC, USA.
VMACXAM causing log messages but no actual errors in processing. Jan 20, 2012 Thanks to Clayton Buck, UniGroup, USA. Change 29.305 Using INTERVAL=SHIFT for RMFINTRV generated MXG WARNINGS VMXGDUR and produced incorrect output, because TYPE75 addition in VMXGINIT Change 29.194 didn't test that INTERVAL value. But after VMXGRMFI the VMXGRMFI fix for SHIFT, and because VMXG70PR uses the VMXGSUM same macros, both summary programs were tested with all Jan 22, 2012 -For RMFINTRV, all "Normally used" INTERVAL= values from SECOND thru FOURHOUR were correct, but for long-duration values of EIGHTHOUR thru ANNUAL, variable STARTIME was a missing value, and an "invalid" string did not circumvent by setting INTERVAL=DETAIL as documented. Changes had to be made to VMXGRMFI where END versus START had been used. -For ASUM70PR and ASUM70LP datasets, there were no errors, but both ASUMCEC and ASUMCELP had populated-but-wrong STARTIME values (close, but wrong) for long-durations. -VMXGDUR was the culprit with inconsistent ENDTIME values returned when FLORCEIL was CEIL for long duration values. (No one reported errors, other than SHIFT, "NEVER USED?") -VMXGINIT added new &MXGDURTM a global macro. -Other members that invoked VMXGDUR were verified to only expect START values, so they didn't need revision here. -VMXGSUM cosmetic: INTERVAL=NONE is no longer printed when no INTERVAL= was specified, as NONE could be confusing. Thanks to Scott Wiig, US Bank, USA.
VMACTMS5 that is not a TMC (because the results are wrong when the Jan 20, 2012 file was created by TMSGRW.) But TYPETMS is also used to read the output of the TMSCLEAN program, to list scratch volumes, so this change allows you to disable that ABEND when you know the file is not a TMC, with this syntax: //SYSIN DD * %LET MXGABND=1; %INCLUDE SOURLIB(TYPETMS5); You will still get the ERROR message on the log that the file was not a TMC as an alert, without the ABEND. Thanks to Robert Carballo, ACS, USA. Change 29.303 Since MXG 27.06, DB2PM-like Statistics Short Report has ANALDB2R had wrong Total GETS and Buffer Totals Hit Ratios values. Jan 19, 2012 The SUM statement in line 18777 repeated QB1 GETS =SUM(QB1TGET,QB1TGET,QB1TGET,QB1TGET,0); but should have summed all four buffer counts: GETS =SUM(QB1TGET,QB2TGET,QB3TGET,QB4TGET,0); Thanks to Paul Billick, QVC, Inc, USA.
IMACICRD but you didn't have an IMACICRD in 'USERID.SOURCLIB', Jan 19, 2012 (listed as required in the UTILEXCL job's report), then the new default IMACICRD in MXG 29.29 was %INCLUDEd, but it had a comment within the commment block (that I had missed in my QA tests) that caused a 180 SYNTAX ERROR. Thanks to Harald Seifert, Huk-Coburg, GERMANY.
VMACNDM Change 29.295 input PSSGPE1D offset, added in V5.0, from Jan 18, 2012 two reserved bytes, but (old) 4.7 PS records have '4040'x in those two bytes, and the NEXT two bytes are zero. Since NDM-CDI records don't contain a version number, the the logic was revised to test the value of the offset vs. the record length to circumvent the error. Thanks to Raff Rushton, IBM Global Services, USA. Change 29.300 First 29.29 ONLY: RMF III PROCESSING WAS BROKEN. ASMRMFV Fixed in 29.29 dated Jan 18: VMACRMFV so that version contains these two corrected members. Jan 18, 2012 -The VMACRMFV member in MXG 29.29 failed when reading DVT EXZRBDVT data with ERROR: INPUT STATEMENT EXCEEDED RECORD LENGTH, Jan 22, 2012 because updates made to VMACRMFV for the new ASMRMFV did not work with RMFBSAM files created with the old ASMRMFV. This change to VMACRMFV revised the DVT logic so that records created by the old or the new ASMRMFV program are correctly processed. -The ASMRMFV member in MXG 29.29 was NOT the updated code, even though it had "Jan 14, 2012, Change 29.297" in the comments and log messages; it was the ASMRMFV from 29.05 that had none of the last six month's enhancements, and it had an R in column 1 of the fourth line which caused the assembly to fail with errors, in the first iteration. -This change MAY be INCOMPATIBLE - the new VMACRMFV might ABEND with RCD data in RMFBSAM files created by earlier ASMRMFV versions, so the ONLY safe implementation is to assemble the Jan 18 ASMRMFV and use that new program to read the VSAM RMF file to create the RMFBSAM output file, and then use the new VMACRMFV to read that RMFBSAM file. (If your existing ASMRMFV load module was created from an MXG version earlier than MXG 29.05, the new VMACRMFV should execute without an ABEND, but no guarantee.) Added Jan 22: -ZRBDVT now only outputs DEVICES WITH ACTIVITY, where the activity is calculated/tested in EXZRBDVT exit member: ACTIVITY=SUM(DEVACTTM,IORATE,DEVIOQTM, DVBUSYTM,CUBUSYTM,SWPODLTM); IF ACTIVITY GT 0 THEN DO; OUTPUT _WZRBDVT; END; Tutorial: Your tailoring logic in EXdddddd dataset exits to control output of an MXG dataset needs this structure: IF something THEN DO; OUTPUT _dddddd; END;
and can't use a DELETE, nor "IF something;" statements, because they stop the read-current-record, and cause SAS to read the next record, so any remaining segments in a record with more than one observation per record would be skipped and the output observation count could be small. -By only outputing active devices in ZRBDVT with detail device-level-per-minute data, it's more practical to use the RMF III detail DVT dataset for DETAIL I/O STATISTICS. Thanks to Jack Schudel, University of Florida, USA. Thanks to Rodger Foreman, TransUnion Corp, USA. Change 29.299 Cosmetic installation issues with first MXG 29.29. FTP -The file size of ter2929.ter was incorrect in the emailed SENDDATA instructions sent on the 17th. 27,319,296 was correct for Jan 18, 2012 that iteration. -Appendix A in the download instructions failed on JES3: IAT4401 LOCATE FOR STEP=STEP2OF2 DD=INFILE DSN=MERRILL.V2929.TERSED IAT4404 DATASET NOT FOUND ON MAIN PROCESSOR A because that DSN was dynamically allocated in the PGM=FTP step, but JES3 doesn't know that. The example is changed to define the DSN in a DD statement, so the new example now works on both JES2 and JES3. This is not a new issue, but had not been previously reported, probably because JES3 techies knew how to resolve this JES3 "feature"! Thanks to Harald Haug, OBERFINANZDIREKTION KARLSRUHE, GERMANY. Thanks to James E. Lund, Texas A&M University, USA. ====== Changes thru 29.298 were in MXG 29.29 dated Jan 17, 2012========= Change 29.298 VMXGPPDS utility reads PDS and PDSE datasets, originally VMXGPPDS to print text in two-column format. It is now enhanced Jan 15, 2012 to output the Index entry for each PDS member, keeping these variables in a dataset for each PDS/PDSE library: MEMBER='MEMBER*NAME' DSNAME='DATASET*NAME' CDATE='CREATE*DATE' MDATE='MODIFIED*DATE' TIME='MODIFIED*TIME' USERID='USER*ID' INITLINE='INITIAL*LINES' NOWLINE='CURRENT*LINES' with an example showing how it can be used to compare the members (i.e., which is most recent?) in different PDS or PDSE libraries. Both text and load libraries can be read, but index information is only usable for text PDS/PDSEs. Change 29.297 Detail and Summary reports from ASMRMFV have been ASMRMFV reformatted for improved legibility, content, and VMACRMFV clarity. Message RMFV105I is updated by the changes. Jan 12, 2012 -When the DVT is selected in ASMRMFV the entries are now blocked up to use as much as possible of a 32K logical record. The number of DVT records output was reduced by 99.5% during testing. The actual data volume is unchanged. This was to reduce I/Os for performance. -A new ASMRMFV report column DATA ACTION shows the data destination for each table as: OUTPUT, FILTER, or SKIP. -A new ASMRMFV report column ENTRIES COUNT shows the number of logical table entries processed. The meaning of an entry varies with the RMF III table type. See source code documentation for more details. -The minimum and maximum LRECL output are now shown for filtered and skipped records if the optional RMFFILT and/or RMFSKIP DD statements are provided. -Input table counts are supported up to 999,999,999. -Output record and entry counts are supported up to 99,999,999,999. -A new message RMFV032E is added to show the error code from the IBM decompression routine ERB3RDEC should a failure occur. In this case the start and end time of the problem RMF III sample set is also shown. This should be a rare event. -The discussion on final ASMRMFV return codes is expanded. -A discussion is added on how RMF Monitor III options affect the data contents in tables. -Prologue documentation in source is updated to include discussion on new ASMRMFV column headings. -VMACRMFV is changed to support blocked DVT entries in input records. -In VMACRMFV the DEVTYPE variable length has been corrected to 12 bytes. -In VMACRMFV the calculation of the DEVACTTM variable has been changed to avoid excessive Missing Value counts from SAS. These are available only with RMF z/OS 1.9 and up. They will be missing values for older releases. -Nine new data variables are added to the ZRBDVT file: DVTFLAG3 - Flag Byte DVTHPAVB - Device Is HyperPAV Base Device (Y/N/?) DVTHPCON - Number Configured HyperPAV Aliases for LSS DVTHPSM - Number of Successful PAV Samples DVTHPNUM - Accumulated Number of HyperPAV Aliases DEVALCH - Number of Alias Exposures Has Changed (Y/N) DEVLCUOK - LCU Number Is Valid (Y/N) DEVPAV - Multiple Exposure Device(Y/N) DEVVDASD - Virtual DASD (Y/N) The first 5 variables are available only with RMF z/OS 1.9 and up. They will be missing values for older releases. The last 4 variables are available to all MXG users with RMF Monitor III. -A new option ZERODVT/NOZERODVT has been added to ASMRMFV. The default is NOZERODVT and will filter out the initial DVT entry for each MINTIME interval. This entry is all binary zeros and has no value in a PDB. -VMACRMFV will also check for a zero initial DVT entry and skip processing for it if detected. -These are companion programs and the same maintenance level of each must be used for successful results, i.e., you MUST assemble the ASMRMFV program to use the VMACRMFV in 29.29.
VMACDCOL by conditionally specifying RECFM=S370VBS when MXG is VMXGINIT executed under ASCII. (On z/OS that DCB parm is set by Jan 14, 2012 the DSCB at OPEN; S370VBS reads V/VB/or VBS RECFMs.) -Variable ZTIME added to all keep lists (zEE time when zEE dataset was created) so that multiple executions of the IDCAMS DCOLLECT process can be differentiated by time. -The alternative to differentiate multiple executions of DCOLLECT is to use the variable INFILENM, which contains Yüklə 28,67 Mb. Dostları ilə paylaş:
|