* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
pattern value could result in a waste of processing resources building an MXG PDB that did not contain the data desired and so that default was inappropriate. -The documentation is updated to make it clear that PATTERR= applies to BOTH pattern AND range errors. There is no RANGEERR= parameter. -DISK is now supported as a value alias for the DEVTYPE= keyword in DVT table filtering so that DEVTYPE=DISK may be used. Any truncation of 'DISK' as a character value (DIS,DI,D) is also allowed. -DVTT= was missing in documentation as an alias for DEVTYPE= although it was always supported. -First message RMFV001I now also displays the system GMT offset as GMT OFFSET=-hh:mm:ss or GMT OFFSET=+hh:mm:ss as extracted from the z/OS Communication Vector Table (CVT) in addition to the existing current date and time of ASMRMFV beginning execution. -A new RMFV001I message shows the ASMRMFV beginning execution date and time in GMT. -A MAXDSNAMES= value exceeding maximum supported &DSNMAX value was not flagged as an error. -Message RMFV034S did not correctly display the number of used table entries when a range or pattern table was exhausted. -Several documentation Sections are updated to support the above changes: Section 5 "Input Data Selection Parameters" Section 8 "Error Handling Parameters" Section 12 "Messages" Section 13 "Filtered Records" Section 17 "Abend Reason Codes" Section 25 "Ranges and Patterns" Section 26 "ASMRMFV and SAS PDB Relationships" (NEW) Section 27 "Summary" Change 33.273 DB2 SMF 102 Trace IFCID=109 INVALID DO LOOP CONTROL ERROR VMAC102 was caused by unexpected/invalid QWT02R10/L/N triplet Nov 12, 2015 with all zeros; which is the only segment in the 109 with QW0109RC, the Bind Return code, so I presumed it was the purpose for the record and did not test for the existence of a non-zero count. Now, I do test, and still output an observation, which will have QW0109RC a missing value. Thanks to Karl-Olaf, JN Data, DENMARK. Change 33.272 Cosmetic change to eliminate numeric conversion messages. ASUMTALO
VMXGRMFI Nov 11, 2015 Change 33.271 TYPETMO2 processing of compressed records did not print VMACTMO2 the warning message if the internal MXG decompression is Nov 11, 2015 used on z/OS instead of the EXITMON6 Infile Exit.
VMAC1415 added by z/OS 2.2 and MXG 33.01, was spelled SMR14ALIAS Nov 10, 2015 in the KEEP= list so it was not kept. With MXG 33.01+ use MACRO _KTY1415 SMF14ALIAS % in your IMACKEEP to keep the variable until you drop in the next MXG Version. Field was added by APAR PI69296. Thanks to Robert Obee, IMS Health, USA.
UTILBLDP generated code is automatically printed on the SAS log, Nov 9, 2015 so we can examine the output without requesting a rerun to enable ECHO, if there is a problem in execution. Change 33.268 -Support for SEVEN USER-USER fields in CICSTRAN, and IMACICVY several other unique fields. IMACICVZ To enable these user fields, you need to specify IMACICWA %LET NREXCLUSER=7; IMACICWB %INCLUDE SOURCLIB(UTILEXCL); IMACICWC _BLDDICT IMACICWD _BLDEXCL IMACICWE _RPTEXCL IMACICWF -Variable JOB is added to CICSTRAN.CICSTRAN (the JOB name IMACICWG of the CICS region). IMACICWH IMACICWI
IMACICWJ IMACICWL
IMACICWM IMACICWN
IMACICWP IMACICWQ
UTILEXCL VMAC110
VMXGINIT Nov 11, 2015 Thanks to Jens Ove Stogaard, NORDEA, SWEDEN.
VMAC120 the offset for the INPUT was not updated by the length. Nov 6, 2015 Thanks to Elie Sawaya, Royal Bank of Canada, CANADA. Change 33.266 MXG 33.11 only. ERROR: VARIABLE SYTPN NOT FOUND, only if VMACXAM _SXAM is used to sort the zVPS datasets; SYTPN should not Nov 6, 2015 be in the new _BXAMCU2 and _BXAMCUV "By List" macros as it does not exist in those two new datasets. Thanks to Matthew Brooks, OPM, USA. Thanks to Robert Richards, OPM, USA. Thanks to Leslie W. Mitchell, OPM, USA.
VMACTPMX are TODSTAMP8. STCK datetimes, so their incorrect INPUT Nov 6, 2015 with &PIB.8.6 and subsequent divide by 4096 was invalidly creating dates in 2076, since that is a duration value (same as MSEC8) rather than a datetime value. Thanks to Scott Barry, SBBWorks Inc., USA. Change 33.264 Support for APPTUNE 11.2 INCOMPATIBLE changes to the 8005 VMAC102 IFCID record. Some truncated 8005 records are created Nov 5, 2015 that MXG detects and reports the first instance, and the Nov 23, 2015 vendor reports a correction will be provided. Datasets T1028004, T1028005, and T102800B have been data-tested. Thanks to Rudi Claes, KBC, BELGIUM. Change 33.263 Support for User CICS field BTMASK. IMACAAAA
IMACICVX UTILEXCL
VMAC110 Nov 4, 2015 Change 33.262 Support for SMF 119 subtypes 41-44 (previously, zero obs) FORMATS and for the below fields added in z/OS 2.1 or earlier VMAC119 that had been overlooked. Nov 6, 2015 -Subtype 2, dataset TYP11902: TTLCLSMCLINKID='LOCAL*SMC-R*LINK*ID ' TTRMTSMCLINKID='REMOTE*SMC-R*LINK*ID' TTSMCREASON ='SMC-R*LINK*FAILURE*REASON*CODE' TSMCFLAGS ='SMC-R*FLAG' FORMAT $MG119RC is created to decode the Reason Code. -Subtype 5, dataset TYP11905: TSSMCRACTIVEOPENED ='ACTIVE*TCP*CONNECTIONS*ACROSS*SMC-R LINKS' TSSMCRACTLNKOPENED ='ACTIVE*SMC-R*LINKS*OPENED' TSSMCRCONNCLOSED ='CLOSED*TCP*CONNECTIONS*ACROSS*SMC-R LINKS' TSSMCRCURRESTAB ='TCP*CONNECTIONS*ACROSS*SMC-R LINKS' TSSMCRCURRESTABLNKS='CURRENT*ACTIVE*SMC-R*LINKS' TSSMCRINRSTS ='SMC-R*INBOUND*WRITE*OPERATIONS*ABNORMAL*CLOSE' TSSMCRINSEGS ='SMC-R*INBOUND*WRITE*OPERATIONS' TSSMCRLNKACTTIMEOUT='SMC-R*LINK*ACTIVATION*TIMEOUTS' TSSMCRLNKSCLOSED ='SMC-R*LINKS*CLOSED' TSSMCROUTRSTS ='SMC-R*OUTBOUND*WRITE*OPERATIONS*ABNORMAL*CLOSE' TSSMCROUTSEGS ='SMC-R*OUTBOUND*WRITE*OPERATIONS' TSSMCRPASLNKOPENED ='PASSIVE*SMC-R*LINKS*OPENED' TSSMCRPASSIVEOPENED='PASSIVE*TCP*CONNECTIONS*ACROSS*SMC-R LINKS' TSTCEPHPORTAVAIL ='AVAILABLE*TCP*EPHEMERAL*PORTS' TSTCEPHPORTEXH ='BIND*FAILS*NO TCP*EPHEMERAL*PORTS' TSTCEPHPORTINUSE ='TCP*EPHEMERAL*PORTS*CURRENTLY*IN USE' TSTCEPHPORTMXUSE ='MAXIMUM*TCP*EPHEMERAL*PORTS*USED' TSUDPBFA='BIND*FAILS*NO*UDP*EPHEMERAL' TSUDPAVA='AVAILABLE*UDP*EPH*EPHEMERAL'/ TSUDPUSE='INUSE*UDP*EPH*EPHEMERAL' TSUDPMAC='MAXIMUM*UDP*EPH*EPHEMERAL'/ TS6CEALO='ECSA*CURRENT' TS6CENIU='ECSA*FREE' TS6CPALO='PRIVATE*CURRENT' TS6CPNIU='PRIVATE*FREE' TS6SMCFC='SMCR*FIXED*CURRENT'/ TS6SMCFM='SMCR*FIXED*MAX' TS6SMCSC='SMCR*SEND*CURRENT' TS6SMCSM='SMCR*SEND*MAX' TS6SMCRC='SMCR*RECV*CURRENT' TS6SMCRM='SMCR*RECV*MAX' -Subtype 6, dataset TYP11906: IFQDXNET='PHYSICAL*NETWORK*ID' -Subtype 7, dataset TYP11907: FFSESSID='FTP*ACTIVITY*SESSION*ID' -Subtypes 41-44, all datasets are now populated. -Subtypes 97. Variable SSH_FSPATH2 now INPUT and kept; The three variables SSH_FSPATH/FSPATH1/FSPATH2 should have been named FCPATH to match their IBM field names. -Variables EXTWTRNM,JESUBSYS,JOB,LOCLINFO,READTIME are not kept in datasets TYP11941/42/43/44/4L, where they don't exist and should never have been kept. Thanks to James T. Sherpey, Bank of America, USA. Thanks to David M. Wrobel, Bank of America, USA. Thanks to Jennifer D. Ayers, West Virginia State Government, USA.
VMAC7072 In dataset TYPE72GO, only two variables are kept for the Nov 4, 2015 calculated percentage variables, PCTxxxxx and VALDSAMP, since the numerator value R723yyyy can be re-calculated in the EXTY72GO exit and KEPT in the _KTY72GO macro in your tailored IMACKEEP. But by changing the variable name in the INPUT to the R723yyyy field name and using it for the PCTxxxxx calculation, those R723yyyy variables can be added to TYPE72GO with only _KTY72GO tailoring, so the EXTY72GO tailoring is not required. The code for the TYPE72MN dataset was similarly revised internally. Thanks to Erling Andersen, SMT, DENMARK. ====== Changes thru 33.260 were in MXG 33.11 dated Nov 2, 2015========= Change 33.260 ANALSMDU report analyzes an SMF file for duplicate data ANALSMDU showing if/when duplicate data exists in separate dump Nov 2, 2015 groups, with record numbers so duplicates can be removed, and tabulating if duplicate data exists in individual SMF dumps. Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA. Change 33.259 Support for zVPS Release 4230 for z13 is SMT mode EXXAMCUV creates two new datasets: EXXAMCU2 dddddd dataset description IMACXAM XAMCU2 XAMCU2 VMACXAM XAMCUV XAMCUV VMXGINIT
Oct 30, 2015 Change 33.258 Support for CICS USER field TORM. UTILEXCL
VMAC110 Oct 30, 2015 Thanks to Don Deckard, Wal*Mart, USA. Thanks to Cheryl Jordan, Wal*Mart, USA. Change 33.257 This change is REQUIRED for CICS/TS 5.3. The final new UTILEXCL CICS/TS 5.3 field, as always inserted, INCOMPATIBLY, VMAC110 DSAPTHWT, is now supported, supported, creating variables Oct 29, 2015 DSAPTHCN='WAIT COUNT*FOR DSA*PATH' DSAPTHTM='WAIT TIME*FOR*DSA*PATH' Field was added in Beta 14. Thanks to Anthony Hirst, Wells Fargo, USA.
VMAC110 IBM CMODIDNT=248 CHMODECT, a four byte counter, but that Oct 29, 2015 was replaced in CICS/TS 1.3 with CMODIDNT=247 DSCHMDLY which is an 8-byte wait duration plus update counter that created these two variables that are now re-labeled: DSCHMDCN='DSCHMDLY*COUNT*TCB*CHANGE MODE*REQUESTS' DSCHMDTM='DSCHMDLY*DURATION*CHANGE MODE*REQUESTS'
UTILEXCL connectors exist; arrays increased to 1999. Oct 27, 2015 Thanks to Erling Andersen, SMT, DENMARK. Change 33.254 MXG 33.09-33.10. Using WORK=SASWORK caused TYPE7072 code VMAC7072 to fail; temporary datasets TYPE70EC and TYPE70EN did not VMXGINIT have &Wdddddd/&Pdddddd in their _Wdddddd/_Ldddddd tokens, Oct 26, 2015 so they were written to //WORK instead of //SASWORK, no Oct 31, 2015 error, but inconsistent. Change 33.217 for z/13+SMT 70's revised MXG code for TYPE70EC/EL/EN datasets had replaced _WTY70EN with DATA TYPE70EN (the same when WORK=WORK), but the VMXGDEL deleted DATASET WORK.TYPE70EN when it should not have. There is nothing illegal about setting Options WORK=SASWORK, and it was previously supported, but it had not been recommended by MXG, and is unneeded since //WORK can be multi-volume. Thanks to Scott Bickel, Kansas State Government, USA.
SAGANAL for each COMMAND in new Report 32. Report 19, PROC PLOT Oct 30, 2015 was removed from _RPTALL as it was only used in testing. Nov 3, 2015 New Report 32 tabulates HOURLY TSO MSU for NAT commands. Change 33.252 IMS Transaction dataset TYPE56FA does not contain SYSTEM, TYPEIMST the MVS SYSTEM ID, but you can pass the SYSTEM name into VMACIMS SAS from each JOB's JCL using the SYSPARM() statement: Oct 22, 2015 // EXEC MXGSAS94,OPTIONS='SYSPARM="SYSA"' or the SYSTEM can be set with SYSPARM in your //SYSIN OPTIONS SYSPARM="SYSA"; Then, inside MXG first-time logic that creates ZDATE and ZTIME, retrieves that value with SYSTEM=SYSPARM(); and variable SYSTEM is RETAINED and OUTPUT in each dataset. -SHIFT was added to all IMS datasets based on IMSSTCK. Only VMACIMS was changed; TYPEIMST is just for reference. -For years, the only JCL for SYSPARM that worked had EIGHT quotes before and FIVE after the text, and I have a 2013 example, but that syntax now fails with SAS 9.4, and SAS now documents the much cleaner double quote syntax. Both IMS and BVIR require you to supply the SYSTEM thru SYSPARM=, and other members use SYSPARM to enable debug. All of the JCL examples with OPTIONS=SYSPARM= now use the double quotes for both instream and in JCL. -Variable ZTIME is added to all IMS datasets that have the ZDATE variable now. Thanks to David A Bernhardt, Verizon, USA. Change 33.251 CICSTRAN variable OSTART=ORIGINATING*TASK*START*DATETIME UTILEXCL was on GMT; MXG overlooked the need to convert it to the VMAC110 local time zone. Oct 20, 2015 Thanks to David Shaw, M & T Bank, USA. Thanks to Douglas Donoho, M & T Bank, USA. ====== Changes thru 33.250 were in MXG 33.10 dated Oct 20, 2015=========
VMAC102 because QWT02R2L is two bytes shorter than the actual Oct 18, 2015 DB2 10.1 records. -SMF 102 IFCID 220 INVALID ARGUMENT appears to be a truly invalid record, with DSNAME where DDNAME should be. The error is circumvented by validating the DHMS arguments while the record is investigated. Variable QW0220OT is the datetime stamp being calculated from characters, and will be missing for invalid input, without the error. Thanks to Joe Babcock, General Motors, USA. Change 33.249 Decoding of DEVCLASS=41 now identifies specific CTC type: VMACUCB DEVTYPE DEVICE Description Oct 15, 2015 previous CTC 05X CTC-OSA OSA 06X CTC-OSAD OSA DIAG DEV 07X CTC-IQD HIPERSOCKETS 09X CTC-OSAN OSA ZBX NETWK 0AX CTC-OSAM OSA ZBX MGMT NETWK 32X CTC-FIC FICON other CTC Thanks to Scott Barry, SBBWorks Inc., USA.
TYPEDOS Only minor changes were required, including protection Oct 13, 2015 for SEGCNT larger than the number of device segments in the record (caused STOPOVER). Change 33.247 -If you use UTILEXCL and have more than four "triplets": VMAC110 WARNING: THE QUOTED STRING CURRENTLY BEING PROCESSED HAS Oct 14, 2015 BECOME MORE THAN 262 CHARACTERS message is printed. This warning has NO impact. Change 33.203 added the text in MACRO _CICXLTR (the list of "triplets" in IMACEXCL) to MXG diagnostic PUT statements about EXCLUDED fields. Each triplet test is one line of text so four triplets exceed a SAS internal limit of 262 character for quoted text in PUT statements in macro resolution. Change 33.203 used $LENGTH CICXLTR $32000; %LET CICXLTR=%QUOTE(_CICXLTR); CICXLTR=SYMGET('CICXLTR'); to store the text in macro variable &CICXLTR, and then used "&CICXLTR" to print the text in the PUT statement, but that's the macro resolution causing the warning! Now, by using CICSXLTR=RESOLVE('_CICXLTR'); to directly store the old-style macro text into the data step variable CICSXLTR, that variable can be used in the PUT statement, with no macro resolution needed and hence no warning message. Sites with SAS 9.1 may need to change RESOLVE to COMPRESS. Contact support@mxg.com. This shows how easy it is to store the text contents of an old-style substitution macro into a variable. -CICS/TS 5.3, close comment missing for TSQIOSCN in the INPUT statement, causing new-in-5.3 variables in CICSRDQU Resource dataset TSQGESTM/GESCN/PUSTM/PUSCN/GESBY/PUSBY to be wrong. -CICS/TS 5.2 MNSEGCL=5 records with MNR5LENT=96 caused STOPOVER because MXG expected 104 (5.3 value). Change 33.246 -Using UTILBLDP with BUILDPDB=YES, if you suppressed type UTILBLDP 6, 26, or 30, the job failed in BUILD005 when it tried ZTILBLDP to process the non-existent datasets. Now, if any of the Oct 20, 2015 datasets are not created, then BUILD005 is suppressed, and warning message is printed. -A second execution of UTILBLDP in the same SAS Session failed with old-style macro errors that are now resolved and UTILBLDP can be re-executed as often as needed. -The changes to support second execution were extensive and thus extensively tested, but, just in case, the prior UTILBLDP from MXG 33.09 is stored in ZTILBLDP. Thanks to Michael Reines, Decadis, GERMANY. Change 33.245 Support for OMEGAMON ATF IMS Log Record LCODE A0 records: EXATFA0 dddddd dataset description IMACATF ATFA0 IMSATFAO ATF IMS LCODE A0 TYPEATF ATFDB IMSATFDB ATF IMS DBD TYPSATF ATFDL IMSATFDL ATF IMS DLI DB TYPEATFI ATFDT IMSATFDT ATF IMS DLI TM TYPSATFI ATFD2 IMSATFD2 ATF IMS DB2 VMACATF ATFMQ IMSATFMQ ATF IMS MQ VMACIMS ATFOA IMSATFOA ATF IMS OTHER A VMXGINIT ATFOB IMSATFOB ATF IMS OTHER B Oct 19, 2015 -Application Trace Facility is a component of Omegamon XE Nov 17, 2015 for IMS v531. Detail trace data from intercepts capture application execution for IMS related threads, including DB2 and MQ API calls from an IMS application. The detail data, possibly millions of intercepts per transaction, is summarized into new IMS LOG A0 record. It's unlikely to trace everything always, so this is not a replacement for the IMS 56FA Log Record (TYPEIMST) for IMS chargeback and response/resource reporting, but there is more data in ATF - notably the DBD information - than in the 56FA, so if selectively enabled for trouble children, it might be a useful source for IMS trouble shooting. -TYPEATFI reads IMSLOG format records, TYPEATF reads the alternate destination, ATFLOG, if that option is chosen. -MXG member TYPEIMS7 is updated to process ATF records if found along with all other IMS Log records. -The IBM default is A0, but that can be changed with the MACRO _IDATF using %LET MACKEEP= tailoring in //SYSIN. -ATF replaces the old ITRF component of Omegamon/XE. -This is the support for Phase I. Additions are coming. -Nov 17: INPUT @LOCVARSEG+ATFXSNzzO syntax is REQUIRED because ATFXSNzzO offset can be zero, and the SAS syntax INPUT @A+B is NOT the same as INPUT @B+A and the first variable MUST ALWAYS BE NON-ZERO. When in doubt, use LOC=A+B; INPUT @LOC.
ANALID the RACFEVNT value is used instead, but now, RACFEVNT is FORMATS INPUT in the SMF Header processing and stored in SUBTYPE UTILBLDP so that the ANALID report will tabulate (and describe, VMACSMF using the updated SMFID format) each type 80 subtype. Oct 10, 2015 And, UTILBLDP selection by SUBTYPE (WANTSMF=80.02) is now supported for ID=80 records. NEVER USE TYPE80/TYPS80, ALWAYS USE TYPE80A/TYPS80A. Change 33.242 Support for z/VM 6.3.15.0 VXSYSPRT (0.02) z13 SMT mode. VMACVMXA New SMT-related variables added to the end of the record. Oct 10, 2015 But: See Change 33.299, REQUIRED.
PDBAUDIT in your BUILDPDB that reports the total number of pages, Oct 9, 2015 variables, size, and bytes in each PDB data library.
IMAC30IO types (EXCP3350/IOTM3350) can be dropped from all TYPE30s Oct 9, 2015 and PDB.JOBS and PDB.STEPS by tailoring IMAC30IO to save disk space (one PDB reduced 400MB from 2500MB to 2100MB). A new example in comment block can be enabled to keep only the variables for current device types. Change 33.239 Some TYPE70 variables can't be DROPped using _KTY70 with VMAC7072 DROP= because the TYPE70 dataset is not created directly Oct 8, 2015 as SMF is read (when _KTY70 is used for TYPE70SP). TYPE70 is created from TYPE70SP and TYPE70PR with multiple DATA DATA steps and Split Record processing. Using _KTY70 also has a risk of dropping a variable needed in the data steps that follow. This change creates _KTY70DR, a null old-style MACRO that can be used to drop any variables in TYPE70 dataset, safely. This syntax in your //SYSIN: %LET MACKEEP= MACRO _KTY70DR DROP= IF: VF: APPC: % ; drops all variables starting with IF, VF, or APPC. Thanks to Scott Barry, SBBWorks Inc., USA. Change 33.238 Support for RACF Flat File of IRRDBU00 record type 1560 EXRA1560 creates new dataset IMACRACF DDDDDD DATASET DESCRIPTION VMACRACF RA1560 RACF1560 GENERAL RESOURCE CERTIFICATE INFORMATION VMXGINIT CERTN_NAME ='GENERAL*RESOURCE*NAME' Oct 8, 2015 CERTN_CLASS_NAME ='GENERAL*RESOURCE*PROFILE*CLASS' CERTN_ISSUER_DN ='ISSUERS*DISTINGUISHED*NAME' CERTN_SUBJECT_DN ='SUBJECTS*DISTINGUISHED*NAME' CERTN_SIG_ALG ='CERTIFICATE*SIGNATURE*ALGORITHM' Thanks to Robert Miles Standish, UBS, USA. Change 33.237 Support for EDA v7706 (INCOMPATIBLE, two existing 8-byte VMACEDA user fields were expanded in place to 20 bytes). There Oct 6, 2015 is no version field in their record; the length of the record for each subtype is now used to create EDAVERS to read either the new or old version records transparently. Thanks to Valentine Wudarczyk, BNYMellon, USA. Change 33.236 DB2 zPARM QWP4xxxx fields marked (S)-SERVICEABILITY were VMAC102 not always kept, but IBM is now using these three fields Oct 14, 2015 QWP4INLP='INLISTP' QWP4MXOS='MAX*OPT*STOR' QWP4SHDE='SUPPRESS*HINT*SQLCODE*DYN' QWP4XMLO='XML*PROCESSING*OPTIONS' The first two were kept but unlabeled. Now all (S) are kept and labeled in T102S106 dataset. The first six have actual labels, the others have their name as LABEL. QWP4ACCS QWP4ADMT QWP4INLP QWP4MXOS QWP4SHDE QWP4XMLO QWP4AST QWP4CDE1 QWP4COC1 QWP4COC2 QWP4CTHR QWP4CUT QWP4FLKT QWP4LTDM QWP4MQTH QWP4MS4A QWP4MXCE QWP4MXOC QWP4MXOE QWP4MXTB QWP4PLIM QWP4RMTI QWP4SCLC QWP4SCTM QWP4SELD QWP4SPC QWP4SPS QWP4STHR QWP4TJTH QWP4TTRS QWP4ULB2 QWP4ULFR QWP4ZUT -Variables QWP4ACCS and QWP4DFID character values were not correct when test was EBCDIC, and QWP4OZTM is now numeric datetimestamp instead of $CHAR8. hex value. Thanks to Lai Fai Wong, Bank of America, USA.
VMAC74 z/OS SITES and MUST BE INSTALLED PRIOR TO DEC 15 2015 to Oct 6, 2015 prevent failure at IPL if the APAR is NOT installed. Yüklə 28,67 Mb. Dostları ilə paylaş:
|