* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
VMAC94 Feb 29, 2004 Thanks to Bruce Widlund, Merrill Consultants, USA. Change 22.014 WebSphere SMF 120 records don't have GMT offset, and the VMAC120 MXG algorithm was wrong, so all of the SM120xxx datetime Feb 27, 2004 variables were wrong, if your GMT offset is non-zero. Some were off by one-GMT-offset, some were off by two! And SM120WAU could still be wrong, if it spans the Spring/Fall time changes, since it can be several days earlier than the SMFTIME of the record. Thanks to Tom Draeger, Aurora Health, USA. Change 22.013 -Members EXNDMIP and EXNDMSP were removed; all references EXNDMIP to NDMIP and NDMSP were removed; the IP and SP subtypes EXNDMQT are output in the NDMDT dataset. EXNDMSP -Member EXNDMQT and all references to NDMQT were removed; EXNDMTI subtype "QT" is output in NDMQE. EXNDMUM -Member EXNDMTI and all references to NDMTI were removed; VMACNDM subtype "TI" is output in NDMCI. VMXGINIT -Member EXNDMUM and all references to NDMUM were removed; Feb 26, 2004 subtype "UM" is output in NDMAE. -Data set Label "NDM AUTHORIZATION" was revised to show the subtypes, for severaly NDM datasets. Thanks to Chris Weston, SAS ITRM, USA. Change 22.012 -Variables RACFUSER & RACFTERM were reversed in MXG code. VMACTMNT -The new subtype 6 stats record from ML-28/ML-29 caused an Feb 26, 2004 INPUT STATEMENT EXCEEDED error; MXG expected ML-30, which which added two new fields. -Pending March 3: some timestamps created in ASMTAPEE are on GMT clock, and support for a bit-changing APAR are in development/testing. Thanks to Tom L. White, SPRINT, USA. Thanks to Jon Whitcomb, Great Lakes Educational Loan Services, USA. Thanks to Normand Poitras, IBM Global Services, USA Change 22.011 Calculation of PCTCPUBY in PDB.TYPE70PR for IRD was not VMAC7072 correct for any engine with SMF70ONT less than DURATM. Feb 24, 2004 The calculation of PCTCPUBY was revised to use SMF70ONT as the denominator instead of DURATM when IRD has varied the engine off during the interval. This only affected the PDB.TYPE70PR dataset; both PDB.ASUM70PR and ASUMCEC with MXG 21.05 (Change 21.170), but see Change 22.050. Thanks to Scott Barry, SBBWorks, USA. Change 22.010 Two typographic errors were corrected; /* before SMCASID RMFMON instead of just /, and in the PUT statement variable name Feb 24, 2004 IRARMCNS instead of IRAMCNS. Thanks to Daniel T. Cannon, The Hartford, USA. Change 22.009 Hyperspace buffers, reads, and writes variables are now VMACMBO input and kept. Feb 24, 2004 Thanks to Job Babcock, Bank One, USA. Change 22.008 -The TPMX arrays were redesigned so that it is no longer EXTYTPMX fatal to have more instances in your data than you %LET IMACTPMX in your IMACTPMX member. A new message will be printed: VMACTPMX ***ERROR.TPMX JBL19NN ARRAY SIZE EXCEEDED. Feb 22, 2004 with the name "JBL19nn" of the %LET statement to change, Feb 24, 2004 but extra instances are skipped and all records are now Feb 25, 2004 output. New variables with the same name as the macro Mar 11, 2004 variable are created in TYPETPMX dataset, so you can use PROC MEANS DATA=TYPETPMX MAX; to see how many instances were found in your data. The %LET statements in IMACTPMX set the number of variables created in each array, and all variables are normally kept, but you can increase the %LET to eliminate the message, and then use the example DROP statements in your EXTYTPMX member, if you don't want to output that many instance variables. -Array names were changed (since they are internal to the VMACTPMX code) and all now match the base of the variable name that are output; the "WHEN" values in the format are also changed for the arrays and also match the base name. -Format "VARNAME" values were also changed to match their array base name. -Bind variables were not output, but are now. -The original count variables are still kept, to prevent a VARIABLE NOT FOUND condition, but those variables can be removed by uncommenting this DROP statement in EXTYTPMX: DROP JBACTC JBAFFC JBBNDC JRBNDC JBDEAC JCAFTC JCBFRC JLLIMC JLIMTC JBVOLC JVVOLC JBLL1C JBLL2C JBLL3C JBLL4C JBLL5C JBLL6C JBLL7C JBLL8C JBLL9C JBL10C JBL11C JBL12C JBL13C JBL14C JBL15C JBL16C JBL17C JBL18C JBL19C JBL20C JBL21C JBL22C JBL23C JBL24C; -Documentation of the syntax of the PROC FORMAT in the IMACTPMX member was (hopefully!) improved. Thanks to Richard S. Ralston, Humana, USA.
VMACEDGR kept in EDGRVEXT dataset; previously it was only INPUT Feb 18, 2004 and kept in EDGRXEXT dataset. Thanks to Ray Bole, IBM Global Services, USA. Change 22.006 Support for Huron/Object Star subtype 23, and corrections EXHRN23 for subtypes 08, 11, 22, 24, 26, which could cause an IMACHURN INPUT STATEMENT EXCEEDED error. New HURN23 dataset is VMACHURN created. The symbol # was removed from labels; they VMXGINIT are not needed and don't always print correctly. Huron Feb 18, 2004 Versions R3 and R4 have been tested with this change. Thanks to Greg Meyer, Isuzu, USA.
EXTY8214 creates new TYPE8214 thru TYPE8219 datasets. EXTY8215 EXTY8216
EXTY8217 EXTY8218
EXTY8219 IMAC82
VMAC82 VMXGINIT
Feb 17, 2004 Thanks to Willy Iven, Fortis Bank, BELGIUM. Change 22.004 New variable ZTIME='ZEE DATETIME*ZEE OBS*WAS CREATED' is IMACZDAT created and retained in member IMACZDAT, which currently VMACEDGS creates the existing ZDATE variable. ZTIME is needed for VMACTMS5 raw data that doesn't have a "datetime" event variable, Feb 17, 2004 like TMS/CA-1 and DFSMS/rmm tape data that are created by taking a "snapshot" of the tape catalog by running a job. The new ZTIME variable can be used to detect or separate multiple runs, and can be used for duplicate observation detection, and can eliminate the need for ITSV sites to tailor MXG exits. Variable ZTIME is kept in TYPETMS5 and TYPEEDGS datasets. Thanks to Christa Neven, KBC BankVVerzekeringsHolding, BELGIUM. Change 22.003 Several new APPLICATION PRM METRICS are now supported and VMACMWUX these variables created in HPUXAPPL dataset. Feb 16, 2004 APPPRMMD='APPPRM*LOGGING*MODE*APP=0*PRM=1?' PRMMEMUT='APPPRM*MEM*UTILIZED' PRMSTATE='APPPRM*STATE' PRMCPUCA='APPPRM*CPUCAP*MODE' PRMCPUEN='APPPRM*CPU*ENTITLEMENT' PRMMEMAV='APPPRM*MEM*AVAILABLE' PRMMEMUP='APPPRM*MEM*UPPERBOUND' PRMMEMEN='APPPRM*MEM*ENTITLEMENT' Thanks to Miguel Fernandez, Information Services International, USA.
FORMATS with format MG116IN: Feb 16, 2004 VALUE MG116IN Feb 17, 2004 0='0:NO INDEX' 1='1:MSG_ID INDEX' 2='2:CORREL_ID INDEX' 4='4:MSG_TOKEN INDEX' 5='5:GROUP_ID INDEX' Index type can be a critical factor in WebSphere MQ message retrieval. With No Index, message retrieval for a browse is sequential, and can take a long time for large queues, since each page must be retrieved to see whether the page contains the message of interest. With indexing it can take only one page retrieval, and the difference can be seconds or even minutes. If the browse is of many messages, the difference can be "many" times the scan of a single queue, since the queue must be scanned for each message retrieved. And this really gets *ugly* if the queue has spilled over to the page set on DASD. -Labels for WQPUTPMS,WQPUT1PM are 'PERSISTENT*CREATED...' instead of 'PERSISTENT*GOT'. MQPUT calls create messages, MQGET calls retrieve messages (either GET-and-delete or BROWSE). And the distinction between NON-PERSISTENT and PERSISTENT is important because the two types should not normally be intermingled in a queue, for performance. Thanks to Don Deese, (CPExpert), Computer Management Sciences, USA Change 22.001 Support for MQ Series counts and times in ASG-TMON/CICS VMACTMO2 adds four variables to MONITASK and Feb 12, 2004 See MXG Tech Note 4.A in Newsletter FORTY-FOUR, 11Feb04. Thanks to Alex Nielsen, The below Change may be required for your MXG 21.21, depending on its internal date. Tape were copied starting Feb 6, and that edition of the MXG 21.21 annual version need this change. But if your CHANGES in your MXG 21.21 indicates Feb 11, 2004, then this change is already installed. Change 21.320 MXG 21.21 final post-QA corrections/incompatibilities: CLRMFV -SEQENGINE=V6SEQ changed to V8SEQ/V9SEQ in CONFIGV8/V9. NOTE: SEQENGINE HAD TO BE RESET TO V6SEQ IN CONFIGV9. in May, 2004, in Change 22.108. CONFIGV8 See MXG Tech Note 4.A in Newsletter FORTY-FOUR, 10Feb04. CONFIGV9 -VMACDB2. Remove line 8259: PUT _N_= 'HAVE 239 '; EXTMNSTS -UTILEXCL. Add a second percent-sign to change line 218 to IMACTMNT %%INCLUDE SOURCLIB(IMACZDAT); UTILEXCL -CLRMFV. Cosmetic. A "NOT" and EQUAL symbols slipped thru VMAC90 and were changed to "NE"; NOTs don't translate well among VMACDB2 platforms, and were removed back in Change 8.093 VMACTMNT -Only if you received MXG on CD: Change line 57 in member VMXGINIT VMACTMNT, removing "DEVNR", changing the line to be: Feb 10, 2004 MACRO _BTYSTS SYSTEM SHIFT INTBTIME % -The CD-only VMACTMNT error was caused by my accidental copying of support for the new TYPESTAT statistics data from the subtype 6 ASMTAPEE ML-30 SMF record, after the ftp and tape files were built. TYPESTAT was validated, but I didn't use TYPSTMNT to test its sort macro. Member EXTMNSTS was added and VMXGINIT updated for TYPESTAT and the sort has been tested in this final iteration. -Variables SMF9029N,SMF9029A,SMF9030I in archaic VMAC90 were renamed A, N, and Y, only in case someone foolishly uses both VMAC90 and VMAC90A in same step. Use VMAC90A. Thanks to George Canning, Abbey National Plc, ENGLAND. Thanks to Vernon Kelley, IBM, USA. LASTCHANGE: Version 22. =========================member=CHANGE21================================ /* COPYRIGHT (C) 1984-2004 MERRILL CONSULTANTS DALLAS TEXAS USA */
Annual MXG Version 21.21 was dated Feb 6, 2004, thru Change 21.319 Last MXG Version 21.08 was dated Jan 28, 2004, thru Change 21.292 First MXG Version 21.08 was dated Jan 25, 2004, thru Change 21.289 Final MXG Version 21.07 was dated Dec 2, 2003, thru Change 21.247 First MXG Version 21.07 was dated Nov 30, 2003, thru Change 21.245 Final MXG Version 21.06 was dated Nov 12, 2003, thru Change 21.230 Second MXG Version 21.06 was dated Nov 10, 2003, thru Change 21.228 First MXG Version 21.06 was dated Nov 7, 2003, thru Change 21.226 MXG Version 21.05 was dated Sep 22, 2003, thru Change 21.183 First MXG Version 21.05 was dated Sep 18, 2003, thru Change 21.181 MXG Version 21.04 was dated Aug 25, 2003, thru Change 21.159 MXG Version 21.03 was dated Jul 28, 2003, thru Change 21.133 MXG Version 21.02 was dated Jun 9, 2003, thru Change 21.101. Second MXG Version 21.02 was dated Jun 5, 2003, thru Change 21.094. First MXG Version 21.02 was dated Jun 3, 2003, thru Change 21.091. MXG Version 21.01 was dated Mar 24, 2003, thru Change 21.051. Annual MXG Version 20.20 was dated Feb 7, 2003, thru Change 20.341. MXG Newsletter FORTY-TWO was dated Feb 8, 2003.
contain the current MXG Technical Notes that used to be put in member CHANGES between Newsletters. New Technical Notes are now added (and now dated!) in NEWSLTRS/Newsletters with each new MXG Version. I. MXG Software Version 21.21 was shipped to all sites by Feb 13. II. Incompatibilities and Installation of MXG 21.21. III. Online Documentation of MXG Software. IV. Changes Log ======================================================================= I. MXG Software Version 21.21, the Annual Version, was sent by Feb 13. MXG 21.21 supports every new version of every new product that you are likely to install this year, especially for MVS systems, including new z/OS 1.5, CICS/TS 2.3, DB2 V8.1, and IMS V8.1 products, and new data added by PTFs, and data for those releases from the monitor vendors IBM, ASG, BMC, Candle, CA, etc. And for ASCII system there are new objects in existing products (NTSMF, TNG) and more support for "sar" and AIX Performance Tool for unix systems. Details provided below.
CONFIGV9 member and MXGSASV90 JCL Procedure member for z/OS execution; for ASCII, use the current AUTOEXEC file. See Change 21.290.
structural changes, you shouldn't have to change any of your current MXG "Tailoring"; you build the Source Library, create/update the MXG Format Library, change the DSNAME/DIRECTORY name to use MXG2121, and run your acceptance test. That's all that should be required.
AUTOEXEC 21.290 Option defaults changed for SAS V 9.1 for ASCII. CONFIGV9 21.290 Option defaults changed for SAS V 9.1 for EBCDIC. ASMTAPEE 21.304 New MXG Tape "Event" Mount/Allocate/Recvr Monitor. TYPE120 21.294 Support for JVM Heap sizes in SMF 120 st 1 and 3. TYPEBE97 21.312 Support for Beta97 User SMF record. TYPEOMVT 21.311 Support for Omegamon/VTAM subtypes 29 and 30. UNIXSAR1 21.309 Support for "sar", "acctcom", "ps" for AIX/SUN unix. UNIXTOP 21.314 Support for "top" unix report. DAILYDSR 21.293 Support for DFSMS/rmm+DCOLLECT in JCLDAYDS example. EMAIL 21.308 Example to email a PROC PRINT to a list of users. SYSLOG 21.307 Example program to read SYSLOG for job events. Major enhancements added in MXG 21.08 SAS V9.1 21.289 Note 49-169 blanks inserted to eliminate note TYPEDB2 21.281 Support for DB2 Version 8.1, COMPATIBLE back to 20.20 TYPE42 21.288 Support for Type 42 Subtype 10 TYPE42VS Vol Sel Fail TYPENDM 21.286 Support more NDM/Connect Direct subtypes, 26 new dset TYPENTSM 21.285 Support for Web Service Cache, WSRM objects. PROCCOPY 21.279 Use MT=DATA with PROC COPY + SELECT for performance. TYPETPMX 21.271 Major enhancement/validation of ThruPut Manager SMF TYPETNG 21.269 Major enhancement/validation of new TNG objects. TYPENETM 21.263 Support for UniCenter NetMaster Automate Services SMF TYPE115 21.262 WebSphere MQ Version 5.3 SM115REL added. TYPE116 21.262 WebSphere MQ Version 5.3 SM116REL added. TYPEDB2 21.259 Using VMXGTIME with DB2 caused GMTOFFDB/QWACBSC wrong BLDSMPDB 21.255 New BLDSMPDB builds SMF PDB Jobstream, weekly, etc. VMXGINIT 21.253 Global macro variables TRENDOLD/TRENDNEW/TRENDINP. RMFMON 21.252 Free Interactive RMF control block monitor. TYPESASU 21.251 Support for SAS SMFEXIT adds SAS Version/User/JOBID. ANALALL 21.250 ANALALL/ANALJOBN/VMXGPRAL job counting SMF records.
TYPEOPFT 21.233 Support for Fujitsu Siemens openFT ftp SMF record. TYPE110 21.240 Support for new S4RSP7CT in STID=124 CICS record. TYPEMWUX 21.241 Revised support for HP Measureware for HPUX. ASUMCICS 21.242 Protection for OPERATOR/TERMINAL variable not found. TYPE74 21.238 Dataset TYPE74DU (RMF DUPLEX CF) was trashed. ANALDB2R 21.239 Ability to read multiple PDBs in ANALDB2R restored. ASUMUOTT 21.237 New ASUMUOTT combines TMDBDB2 and MONITASK datasets. ASMRMFV 21.236 Wrong member replaced; this has change 21.186 code. UTILBLDP 21.231 USERADD=80/90 create TYPE80A or TYPE90A execution. Major enhancements added in MXG 21.06 ASUMUOW 21.220 FLASH: MXG 21.06 required to have all errors fixed. TYPETSMF 21.210 Support for IBM Tivoli Storage Manager Acct Records. TYPE102 21.175 Support for IFCIDs 217 and 254. TYPETNG 21.160 Support for TNG Version 7 (INCOMPAT, Header changed). TYPE99 21.217 Support for SMF 99 subtype 7 PAV Device record. TYPE80A 21.215 Support for EKC's ETF/R FIRECALL SMF 80 data. TYPEORAC 21.213 Support for Oracle V9.x, no changes. TYPE110 21.212 Support for CMODNAME='MQSeries' CICSTRAN segment. TYPE110 21.152 Support for CICS/TS 2.3 (INCOMPATIBLE)in MXG 21.05+. TYPE80A 21.211 Support for RACF segment RACFDBP=44, new variables. TYPECIMS 21.205 Support for Shared Message Queue Group in SMQGROUP. TYPEEXCH 21.195 Support for Microsoft Exchange Server 5.5 Log file. TYPE119 21.190 Support for APAR PQ77633, corrects FTPREPLY. none 21.184 Support for 3592 Tape Drives, they look like 3590s. TYPESYNC 21.192 Up to 255 SORTWORKs supported in z/OS 1.1 SMF record. RMFINTRV 21.225 RMF WORKLOAD name can be used to define workloads. TYPE70 21.170 NRCPUs in TYPE70 redefined to Average Online for IRD. RMFINTRV 21.170 NRCPUs in TYPE70 redefined to Average Online for IRD. TYPEDB2 21.200 Negative values for DB2TCBTM if QWACEJST small. TYPE110 21.198 Missing value for STRTTIME in CICSTRAN possible. VMXGSUM 21.185 New INTERVAL=SECOND now supported. CONFIGV8 21.168 SORTSEQ=EBCDIC or SORTSEQ=ASCII forced default. RMFINTRV 21.216 z990 CPUTYPE 2084 NOT IN TABLE with OS/390 R2.10. TYPE6 21.210 Support for several ESS segments '34x,35x,37x,47x'. TYPEDB2 21.208 QWACBSC/QWACESC missing in DB2ACCTP, some packages ASUMCACH 21.197 Enhanced to keep I/O by LPAR in PDB.ASUMCACH. TYPE110 21.189 New 110 St=1 MNSEGCL=5 caused INVALID DO LOOP CONTROL
RMFINTRV 21.170 NRCPUs in TYPE70 redefined to Average Online for IRD. TYPE110 21.176 New TSQUEUE SMF 110 CL 5 INPUT STATEMENT EXCEEDED. TYPE110 21.165 STID=126 UNEXPECTED data corrected. TYPE102 21.175 Support for IFCIDs 217 and 254. TYPE116 21.173 Subtype 0 SMF 116 INVALID PRODUCT SECTION message. TYPE119 21.162 IFDURTM was incorrectly divided by 496 vice 4096. TYPETNG 21.160 Support for TNG Version 7 (INCOMPAT, Header changed). TYPEWWW 21.166 IIS Web Log with missing fields now supported CONFIGV8 21.168 SORTSEQ=EBCDIC or SORTSEQ=ASCII forced default. MONTHBLD 21.163 Enhancement for un-sorted input, or NOT SORTED ERROR.
While the support for z990s was in MXG 21.04, it was not realized that MXG 21.04 is REQUIRED for z990s until 16Sep. ASUM70PR 21.149 Major LPAR Measurement Enhancement: PDB.ASUM70LP. ASMTAPES 21.137 ASMTAPES new Allocation Recovery event record. UTILBLDP 21.148 Enhancement to the "Build your own PDB" utility. TYPEEDGR 21.158 Support for z/OS 1.4 DFSMS/rmm EDGRXEXT (INCOMPAT) TYPECTLL 21.156 Support for Control-D Log file. TYPENSPY 21.155 Doc: support for NetSpy V6 or V7 in MXG 20.10+. TYPECIMS 21.153 Support for BMC MVIMS IMF 3.3.0 (COMPAT) TYPE120 21.150 Support for CPU Time in WASserver APAR PQ74463. ASUMUOW 21.147 Near-constant value STRTTIME error in PDB.CICS. TYPENTSM 21.146 Support for Windows 2003 Server MEMORY object. TYPEHMF 21.143 Support for HMF Subtype 29,30,32,33 changes. TYPETCP 21.142 TYPETCPS contained accumulated, not interval data. FORMATS 21.141 $MG070CP updated for MSU for CPUTYPE 084 table. TYPEDB2 21.140 PDB.DB2STATS QBGLxxxx wrong, negative B3HITRAT. TYPE7072 21.138 R723Rxxx vars now kept in TYPE72DL vice TYPE72SC. TYPENTSM 21.136 SMPTSERV for Windows 2000 had accumulated values. ANALSTC 21.135 Report using STK SMF + MXGTMNT to track Virtual tape. ANALDB2R 21.157 Accounting Summary Class 2 were totals, not avgs.
TYPE102 21.121 Support for IFCID 251, 257, corrections for 21. TYPE103 21.115 Support for APAR PQ71799 HTTP Server SMF 103 data. TYPE120 21.107 Support for WebSphere APAR PQ74463 - adds CPU time. TYPETMMQ 21.129 Support for ASG-Landmark TMON for MQ Series. TYPENDM 21.133 Support for NDM Release 4.3 (INCOMPATIBLE). TYPEENTX 21.124 Support for EntireX user SMF accounting record. TYPEICE 21.102 Support for STK IXFP SMF L2P00A2/LZP00A9 (COMPAT) TYPEQACS 21.118 Support for TCP and TCPIEF objects for AS/400. TYPEMVCI 21.117 Support for Mainview for CICS 5.6 CMRDETL (INCOMPAT). TYPEAIX 21.116 Major revision to AIX PTX Support - new datasets. VMXGRMFI 21.125 Different SRVCLASS definitions can map to same WORK. Incompatible revision: If you used ASUMCICS to read ASG-TMON/CICS MONITASK to create PDB.CICS, you must now instead use ASUMCICT. But MXG recommends you no longer use either ASUMCICS nor ASUMCICT, but instead you should use ASUMUOW/ASUMUOWT to create PDB.ASUMUOW, and then create PDB.CICS using ASUMCICX to properly measure CICS. See the discussion in Change 21.105 text. ASUMCICS 21.105 Reads only CICSTRAN, creates PDB.CICS, don't use. ASUMCICT 21.105 Reads only MONITASK, creates PDB.CICS, don't use. ASUMCICX 21.105 Reads PDB.ASUMUOW; use instead of ASUMCICS/ASUMCICT. ASUMUOW 21.105 Combines CICSTRAN,DB2ACCT, creates PDB.ASUMUOW, use! ASUMUOWT 21.105 Combines MONITASK,DB2ACCT, creates PDB.ASUMUOW, use! Major enhancements added in MXG 21.02 TYPE7072 21.065 Support for more than 16 CPUs or LPARs. TYPE74 21.058 Support for APAR OW54347 CMR Command Response time TYPETMS5 21.097 Support for PDC # QI30130 new variables. TYPEIMS7 21.064 Support for IMS Version 8.1, some changes. ASMIMSL6 21.064 Support for IMS Version 8.1; just reassemble L6. IMAC6ESS 21.082 Support for additional GPARMKY values in SMF 6 ESS. IMAC6ESS 21.096 Support for GEPARMKY=001B. TYPE30 21.086 Support for IDMS PerfMon type 30 subtype 3 per tran TYPENTSM 21.063 Support for NTSMF 2.4.5 (INCOMPATIBLE). TYPENTSM 21.053 Support for NTSMF BlackBerry Server object. TYPETNG 21.095 Support for six new TNG objects, new fields. EXUTILEX 21.069 Exit for UTILEXCL for non-standard "User" field. VMXGRMFI 21.067 Examples to invoke RMFINTRV twice, general cleanup. ASUMUOW 21.062 Revised SPINUOW logic, forward sequence of times. ASUMUOW 21.093 Blank SYSTEM in PDB.ASUMUOW for CICS-only fixes. Yüklə 28,67 Mb. Dostları ilə paylaş:
|