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



Yüklə 28,67 Mb.
səhifə35/383
tarix17.01.2019
ölçüsü28,67 Mb.
#98988
1   ...   31   32   33   34   35   36   37   38   ...   383

DLRDMR='DL/I*MR*CALLS'

in existing reserved bytes.

Change 33.297 -Label for PCTCPUBY was corrected for PDB.TYPE70EN, which

VMAC7072 had incorrectly been "LPAR*CPU*BUSY".

VMXGWORL -VMXGWORL enhanced to parse the result into two macro vars

Dec 10, 2015 &MXGWORLLIB and &MXGWORLDSN so that PROC DATASETS, which

requires them separately, could be used to change labels.


Change 33.296 If you specified IMACKEEP= to retain the IMACKEEP that is

UTILBLDP generated, invalid syntax for _TIMEDIF/_SPINUOW/_SPINCNT

Dec 9, 2015 could be generated; the NULL value default should have

suppressed the generation of these macros; now it does.

The ECHO=YES default will now display the IMACKEEP text.

Thanks to Richard Krueger, Sentry, USA.


Change 33.295 Cosmetic. Prints messages when there are datasets in OLD

VMXGCOMP that are not in NEW, or vice versa.

Dec 8, 2015
Change 33.294 INPUT EXCEEDED ERROR for SMF 102 records written by BMC's

FORMATS Mainview for DB2, IFCIDs 815Ex-8160x - Accounting Rollup

VMACDB2H and IFCID 80F1x - Data Collector, which were unknown and

Dec 9, 2015 unsupported in MXG. These records contain unique SMF 102

Dec 18, 2015 header segments that do not match MXG expectations that

caused the error. But since no one has actually asked

for these subtypes, this change circumvents the problem

Decimal IFCIDS deleted are 33009,33118,33119,and 33120.

by skipping these subtypes in SMF 102 processing in MXG.

-The ANALID report (VMACID,FORMATS) is updated to be aware

of and describe these 102 subtypes in its reports.
Change 33.293 MACRO _TIMEDIF % set instead of MACRO _TIMEDIF 0 % caused

UTILBLDP a 22-322 Syntax Error.

Dec 5, 2015
Change 33.292 When printing of the found datasets is requested, the

VMXGFIND heading has the LIBNAME and MEMNAME printed.

Dec 5, 2015
Change 33.291 Support for BMC Mainview for CICS Version 7.0 (COMPAIBLE)

VMACMVCI adds these new variables for CICS/TS 5.3 to CMRDETL:

Dec 6, 2015 T6E70XCT='70*EXTENSIONS*LENGTH'

T6EDSAWC='ALLOCATE*THREAD*WAIT*COUNT'

T6EDSAWF='ALLOCATE*THREAD*WAIT*FLAG'

T6EDSAWT='ALLOCATE*THREAD*WAIT*TIME'

T6EEIBTR='INTERNAL*PROCESSING*FIELD'

T6EJSRPL='JSON*RESPONSE*MSG LENGTH'

T6EJSRQL='JSON*REQUEST*MSG LENGTH'

T6ELSTN_ACPTOK ='SUCCESSFUL*ACCEPTS'

T6ELSTN_CHILDTK='CHILD*SUBTASKS*STARTED'

T6ELSTN_DISPROG='DISABLED*PROGRAM'

T6ELSTN_DISTRAN='DISABLED*TRANSACTION'

T6ELSTN_GVSKTFL='GIVESOCKET*FAILURES'

T6ELSTN_REJAUTH='REJECTED*NOT AUTH'

T6ELSTN_REJSECU='REJECTED*SECURITY'

T6ELSTN_REJTDIO='REJECTED*TD*I/O'

T6ELSTN_REJTDLN='REJECTED*TD*LENGTH'

T6ELSTN_REJTDNS='REJECTED*TD*NO SPACE'

T6ELSTN_TACPTOK='TERM*SUCCESSFUL*ACCEPTS'

T6ELSTN_TCHILDTK ='TERM*CHILD*SUBTASKS*STARTED'

T6ELSTN_TDISPROG ='TERM*DISABLED*PROGRAM'

T6ELSTN_TDISTRAN ='TERM*DISABLED*TRANSACTION'

T6ELSTN_TGVSKTFL ='TERM*GIVESOCKET*FAILURES'

T6ELSTN_TREJAUTH ='TERM*REJECTED*NOT*AUTH'

T6ELSTN_TREJSECU ='TERM*REJECTED*SECURITY'

T6ELSTN_TREJTDIO ='TERM*REJECTED*TD*I/O'

T6ELSTN_TREJTDLN ='TERM*REJECTED*TD*LENGTH'

T6ELSTN_TREJTDNS ='TERM*REJECTED*TD*NO SPACE'

T6ELSTN_TUNDTRAN ='TERM*UNDEFINED*TRANSACTION'

T6ELSTN_UNDTRAN='UNDEFINED*TRANSACTION'

T6ENCGET='COUNTER*DCOUNTER*REQUESTS'

T6ETOTL_TINITT ='TOTAL*INIT*TIME'

T6ETOTL_TOTHRT ='TOTAL*OTHER*TIME'

T6ETOTL_TREADT ='TOTAL*READ*TIME'

T6ETOTL_TSLCTT ='TOTAL*SELECT*TIME'

T6ETOTL_TWRITT ='TOTAL*WRITE*TIME'

T6ETRUE_ATTACH ='DYNAMIC*SUBTASK*COUNT'

T6ETRUE_INITCKC='INIT*CALL*COUNT'

T6ETRUE_INITCKF='INIT*CALL*FLAG'

T6ETRUE_INITCKT='INIT*CALL*CLOCK'

T6ETRUE_OPENAPI='OPEN*API*COUNT'

T6ETRUE_OTHRCKC='OTHER*CALL*COUNT'

T6ETRUE_OTHRCKF='OTHER*CALL*FLAG'

T6ETRUE_OTHRCKT='OTHER*CALL*CLOCK'

T6ETRUE_READCKC='READ*CALL*COUNT'

T6ETRUE_READCKF='READ*CALL*FLAG'

T6ETRUE_READCKT='READ*CALL*CLOCK'

T6ETRUE_REUS ='REUSABLE*COUNT'

T6ETRUE_SLCTCKC='SELECT*CALL*COUNT'

T6ETRUE_SLCTCKF='SELECT*CALL*FLAG'

T6ETRUE_SLCTCKT='SELECT*CALL*CLOCK'

T6ETRUE_TATTACH='TERM*DYNAMIC*SUBTASK*COUNT'

T6ETRUE_TCBLIM ='TCB*LIMIT*REACHED*COUNT'

T6ETRUE_TINIT='TASK TERM*TOTAL INITS'

T6ETRUE_TOPENAPI ='TERM*OPEN*API*COUNT'

T6ETRUE_TOTHR='TASK TERM*TOTAL OTHERS'

T6ETRUE_TREAD='TASK TERM*TOTAL READS'

T6ETRUE_TREUS='TERM*REUSABLE*COUNT'

T6ETRUE_TSLCT='TASK TERM*TOTAL SELECTS'

T6ETRUE_TTCBLIM='TERM*TCB*LIMIT*COUNT'

T6ETRUE_TWRIT='TASK TERM*TOTAL WRITES'

T6ETRUE_WRITCKC='WRITE*CALL*COUNT'

T6ETRUE_WRITCKF='WRITE*CALL*FLAG'

T6ETRUE_WRITCKT='WRITE*CALL*CLOCK'

T6ETSGSC='SHARED*TS*GETS'

T6ETSPSC='SHARED*TS*PUTS'

In addition, these existing file segments that have no

extended data now create these variables:

PSEUDOFILE='PSEUDO*FILE*NAME'

PSEUDOFILT='PSEUDO*FILE*DURATION'

PSEUDOFILC='PSEUDO*FILE*COUNT'

ADABASFILE='ADABAS*FILE*NAME'

ADABASFILT='ADABAS*FILE*DURATION'

ADABASFILC='ADABAS*FILE*COUNT'

SAPFILE='SAP*FILE*NAME'

SAPFILT='SAP*FILE*DURATION'

SAPFILC='SAP*FILE*COUNT'

DATACOMFILE='DATACOM*FILE*NAME'

DATACOMFILT='DATACOM*FILE*DURATION'

DATACOMFILC='DATACOM*FILE*COUNT'

IDMSFILE='IDMS*FILE*NAME'

IDMSFILT='IDMS*FILE*DURATION'

IDMSFILC='IDMS*FILE*COUNT'

SUPRAFILE='SUPRA*FILE*NAME'

SUPRAFILT='SUPRA*FILE*DURATION'

SUPRAFILC='SUPRA*FILE*COUNT'

S2KFILE='S2K*FILE*NAME'

S2KFILT='S2K*FILE*DURATION'

S2KFILC='S2K*FILE*COUNT'

GENFILE='GEN*FILE*NAME'

GENFILT='GEN*FILE*DURATION'

GENFILC='GEN*FILE*COUNT'
Change 33.290 The ANALID report tabulates all SMF data in the SMF file;

ANALIDDY the new ANALIDDY tabulates the SMF data by DATE of the

TYPEIDDY SMFTIME so day-to-day counts can be compared.

VMACID The syntax for the new report is:

VMACIDDY

Dec 4, 2015 %ANALIDDY(READSMF=YES,PRINT=YES,PDBOUT=WORK);

Dec 5, 2015

Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA.


Change 33.289 z/OS only. If you used BLDSMPDB to build a MONTHLY PDB:

BLDSMPDB -If the 1st of the month fell on a Sunday then the code

Dec 3, 2015 miscalculated the start of the last weekly and caused

the last few days of the month to be missing.

-If the 1st of the month did not match the start of the

week then the last few days were duplicated because the

logic looked for daily data GE then the start of the

week and should have looked for GT.


Change 33.288 Reserved Change.
Change 33.287 -The PDB.CICDS CICS Dispatcher Statistics dataset now has

ADOC110 variable DSxPCT='AA TCB*PERCENT*USAGE', the IBM estimate

VMAC110 of each CICS TCB's percentage usage.

Dec 3, 2015 -ADOC110 now documents the new TCBs added in CICS/TS 2.2.


====== Changes thru 33.286 were in MXG 33.12 dated Dec 1, 2015=========
Change 33.286 Six TYP1194L variables LxLCLLNKID and LxRMTLNKID were

VMAC119 incorrectly changed from numeric to character in first

Dec 1, 2015 33.12. They were corrected in final Dec 1 refresh.

All six are formatted with HEX8 format for consistency.

Thanks to Jim Horne, Lowe's, USA.
Change 33.285 Cosmetic, eliminate non-impacting warning that numeric

ASUMTALO variable AVGDRIVE has different lengths in ASUMTALO and

TRNDTALO TRNDTALO, because an ancient statement in member ASUMTALO

Nov 30, 2015 specified LENGTH AVGDRIVE 4 while TRNDTALO invoked

VMXGSUM which sets LENGTH DEFAULT=&MXGLEN that is the

correct syntax to set stored length 5 on EBCDIC or 6 on

ASCII, which are the required lengths for SAS variables

that fully support 4-byte input fields. Observed in QA.


====== Changes thru 33.284 were in MXG 33.12 dated Nov 27, 2015=========
Change 33.284 Warning message in TYPE26J2 that the MXG created variable

VMAC26J2 INREASON is blank is removed; not all purge records have

Nov 27, 2015 enough information to populate the created variable, e.g.

JCL error in INTRDR populates only READTIME, JPURTIME and

SYSREAD.

Thanks to Jim Horne, Lowe's, USA.


Change 33.283 -INVALID DATA for WORD5UP in BBBP ENDING UPTIME because

VMACNMON the expected HH:MM format is sometimes 'HH HRS' when the

Nov 26, 2015 value is 'HH:00'. The HRS text is now removed so the 11

hour value is valid eliminating the error message.

-NMON records missing data and the LF delimiter exist and

they cause strange errors.

-One record with TYPE of DISKBSIZEAAA is clearly missing

data and an LF before the AAA, which is a new record

TYPE. This record caused an INVALID ARRAY error because

MXG tested for TYPE=:'DISKBKSIZE', starting with, for

possible numeric suffixes often used in NMON.

-Another record had only CPAAA, causing an UNKNOWN TYPE

log message.

-A third TYPE=LPAR has 22 valid fields but was missing

the LF separator and had a valid AAA record concat.

This record caused an INVALID INPUT error because MXG

expected numbers in the up to 24 fields in TYPE LPAR.

-Because NMON is character data, all numeric fields are

created with INPUT() functions, but now, with these bad

data records, the INPUT functions are now protected with

the ?? token to suppress the ERROR, PUT _ALL_, and LIST

log messages.

-Disk error messages "NRCOUNTERS NE DSKSEQNR" that were

cited as due to bad data in Change 31.164 are corrected.

They were due to new DISKBUSY1/DISKREAD1/etc objects that

NMON created when there were more than 150 devices that

were NOT supported until now.

Thanks to Steve McCulloch, TMX/CDS Group, CANADA.


Change 33.282 SMF 90 records contain the ENCRYPTED/MASKED UTOKEN value

FORMATS as documented in Change 33.189, which noted IBM does plan

VMAC90A to change to the UNMASKED value, but the encryption logic

Nov 25, 2015 is only an Exclusive OR with '55'x and mapping the result

Nov 27, 2015 into a one byte character which is then INPUT as $EBCDIC,

Dec 1, 2015 so the TOKxxxxx variables in the TYPE90A dataset are now

plain text values if the field was MASKED.

-The 80-byte SMF90T37UTOKEN is decoded into its TOKxxxxx

variables, now set to LENGTH $8 (they are INPUT() with a

SUBSTR() which defaults to length of the input variable),

and so it is no longer kept.

-New FORMAT MGHEXNM was needed to map the XOR value to the

character hex value for the output.

-Dec 1: Error +; was corrected.

Thanks to Peter Relson, IBM z/OS Development, USA.
Change 33.281 A valid WARNING was printed from an SQL step due to a

VMXGSIZE WHERE clause. Logic reordered to eliminate the warning.

Nov 24, 2015
Change 33.280 PDB.TYPE70 for z13 in SMT mode could have the wrong count

VMAC7072 in ZIPCPUS, ZIP70PAT, and ZIPUPTM because SMF70PAT was

Nov 21, 2015 incorrectly added to ZIP70PAT when SMF70ONT is missing.

Thanks to Joachim Sarkoschitz, DATEV, GERMANY.


Change 33.279 -Support for DB2 Simulated Buffer Pool statistics segment,

ANALDB2R creates new PDB.DB2STSBP dataset with per pool data, and

ASUMDBSS four sets of QBnSxxxx interval totals in PDB.DB2STATS and

EXDB2SBP ASUMDBSS creates new ASUMDBSP summary dataset.

IMACDB2 -MOBILEWORK programs QAMOB and MOBWRK02 required updates

MOBWRK02 to support/protect this new dataset

QAMOB -Buffer Hit Ratios for the SBP are created but set to a

READDB2 missing value, pending data for validation.

VMACDB2 -ANALDB2R compile fakers for QWxxxxDB were corrected.

VMXGDBSS -The names of tokens/datasets for SBP mirror STB:

VMXGINIT DB2STB DB2SBP

Nov 18, 2015 DB2STSTB DB2STSBP

Nov 22, 2015 DB2STAB DB2STSB

Nov 23, 2015 ASUMDBSB ASUMDBSP

Nov 26, 2015 MACSTAB MACSTSB

Dec 18, 2015 D2BPSIN D2SBPIN

D2SBPIN D2SBPOU

-There is no count of pages-not-in-the-pool so there is no

buffer hit ratio for the simulated buffer pool that I can

calculate. Variable QBSPREADS is the total number of

requests that caused a read.

Thanks to Lai Fai Wong, Bank of America, USA.


Change 33.278 If you used INTERVAL=MONTH, MXGDURTM was missing for the

VMXGDUR 31-day months, except December, when it was non-missing

Nov 18, 2015 but was 41 days of seconds, because the statement

IF MONTH IN(1.3.5.7.8.10,12) THEN MXGDURTM=41*86400;

should have been

IF MONTH IN(1,3,5,7,8,10,12) THEN MXGDURTM=31*86400;

periods are not allowed, but do NOT create a SAS error.

This is old, present in MXG 30.09 but not in MXG 26.26.

Thanks to Chris Weston, SAS Institute ITRM, USA.
Change 33.277 If you tried to use Example TWO to create ASUMUOW, an

IMACUOW error resulted due to a misplaced percent sign; Example

Nov 19, 2015 THREE did not tell you how to create "MYDATA", and while

Example FIVE did work, it was inconsistent with others.

Thanks to Chris Weston, SAS Institute ITRM, USA.
Change 33.276 RMF III variables GEILF4K and GEILP4K in dataset ZRBGEI

VMACRMFV were reversed in their INPUT order; GEILF4K precedes

Nov 16, 2015 GEILP4K now.

Thanks to Kurt Gramling, Total Systems.


Change 33.275 Assemble/Link Edit all five MXG ASM programs for install.

ASMRMFV The existing single ASM/LKED members are restructured so

CICSIFUE the ASM code is isolated from the JCL so the new JCLASMXG

EXITCICS member will create all five loadlib members in one job.

JCLASMXG ASMRMFV - Used in JCLRMFV to process RMF III VSAM file,

MNVWIFUE output RMFBSAM read by TYPERMFV.

MXGTMNT (Individual ASM/LKED is in JCLASM3/ASMRMFV)

TMONEXIT CICSIFUE - Used in TYPEDB2/TYPE110/TYPE112 to decompress

Nov 16, 2015 IBM SMF records 100, 101, 102, 110, and 112

Nov 23, 2015 SMF records.

Nov 27, 2015 (Individual ASM/LKED is in EXITCICS)

MNVWIFUE - Used in TYPEBBMQ to read compressed BBMQVSAM

and in TYPECMFV to read BMC MainView data.

(Individual ASM/LKED is in ASMMNVW)

MXGTMNT - The MXG Tape Mount Monitor Program, read by

TYPETMNT


(Individual ASM/LKED is in ASMTAPEE)

TMONEXIT - Used in TYPETMO2 to decompress MONICICS

TMON/CICS data.

(Individual ASM/LKED is in EXITMON6)

The original documentation comments are in appendices

at the end of JCLASMXG.

Thanks to MP Welch, Bank of America, USA.
Change 33.274 -Enhancement for character data filtering for RMF Monitor

ADOCRMFV III CSR (Common Storage Remaining) table and other

ASMRMFV usability improvements.

Nov 16, 2015 -These filters are intended for building ad hoc MXG RMF

III PDBs for studies avoiding the overhead of generating

a full CSR table based PDB. They control which CSR table

entries are output to the RMFBSAM file.

-Four new filters are added to support CSR entry selection

from this table to the RMFBSAM output file. These

filters are effective only if the CSR table is selected.

They are applied in the order shown when multiple

different keywords are used.


New Keyword Aliases

------------ -----------------------------------------

CSRJOBNAME= CSRJOBNA=, CSRJOBNM=, CSRJOB=, CSRJN=

CSRJESID= CSRJESNO=, CSRJESNUM=, CSRJESNR=, CSRJID=

CSRAND None

CSROR None


-TUTORIAL:

Ranges of the form keyword=first:last may be used with

any of the above keywords except CSRAND and CSROR.
The colon character ':' is required for a paired range

specification. All entries GE the first value and LE the

last value are selected for output to the RMFBSAM file.
The first value may not exceed the last value in EBCDIC

collating sequence or an error is flagged.


Single unpaired values may be specified for a range

simply as keyword=first and in this case the colon ':' is

omitted.
Patterns may also be used with any of the above keywords

except CSRAND and CSROR and include one or more Wild Card

characters to match the respective CSR data field.
A pattern contains one or more special Wild Card

characters as follows:


Wild

Card Matches

---- -------------------------------------------------

* 0 or more characters

% 1 Non-blank character

+ 1 Numeric character (0-9)

_ 1 Alphabetic character or _ (a-z, A-Z, _)

. 1 National character (@, #, $)

! 1 Special character (not a-z, A-Z, 0-9, @, #, $)

? A blank string if used by itself

? 1 Blank character (X'40') if used with any other

characters


Ranges may not be wild carded. If wild carded the range

value becomes a pattern instead and is processed as such.


See Section 25 "Ranges and Patterns" in the ADOCRMFV

member or ASMRMFV source code for more details on usage

of ranges and patterns.
-CSRJOBNAME= selects CSR entries by 1-8 character z/OS

Job Name. Job Name characters are validated to those

allowed by JCL syntax. Both ranges and patterns with

wild cards may be specified. Up to 64 ranges and 64

patterns are supported. The default is CSRJOBNAME=ALL.
-Examples for CSRJOBNAME= :

CSRJN=PROD1234:PROD5678 selects only address spaces with

a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a

range. Note use of the keyword alias CSRJN for coding

convenience.
CSRJOBNAME=.* is a pattern that selects only address

spaces with a Job Name that begins with a national

character.
CSRJOBNAME=*++ is a pattern that selects only address

spaces with a Job Name that ends with 2 numeric digits.


CSRJOBNAME=ABC:ABC88888 is a range that selects only

address spaces with a Job Name that is GE 'ABC ' and

LE 'ABC88888'.
-CSRJESID= selects CSR entries by 8 character JES Job

Identification. Both ranges and patterns with wild cards

may be specified. Since a JES Id is one subsystem

character followed by 7 digits or three subsystem

characters followed by 5 digits not all pattern

characters may be used with this keyword.


See Section 25 "Ranges and Patterns" in the ADOCRMFV

member or ASMRMFV source code for more details on usage

of ranges and patterns.
-For convenience any leading zeros in the numeric portion

of the JES Id may be omitted and will be filled in

automatically. Up to 64 ranges and 64 patterns are

supported. The default is CSRJESID=ALL.


-Examples for CSRJESID= :

CSRJID=J0000100:J0001123 is a range that selects all

address spaces with batch JES Id numbers GE 100 and LE

1123. Note use of keyword alias CSRJID for coding

convenience.
CSRJID=J100:J1123 is a range that selects the same

address spaces as above with the leading zeros omitted

for coding convenience.
CSRJESID=JOB12345:JOB32001 is a range that selects all

address spaces with batch JES Id numbers GE 12345 and LE

32001 for installations with 5 digit JES Id numbers as a

range.
CSRJESID=J1* is a range that selects all address spaces

with a JES ID that begins with 'J1'. This would include

J1000000 through and including J1999999.


-CSRAND (default) indicates that selection results from

the two different CSR filter keywords are logically

ANDed.
-CSROR indicates that selection results from the two

different CSR filter keywords are logically ORed.


-Examples of CSRAND/CSROR:
With CSRAND (default) in effect:

CSRJESID=J10* CSRJOBNAME=XYZ*

are two patterns that select ONLY jobs whose JES ID

begins with 'J10' AND Job Name begins with 'XYZ'.

CSRAND provides more restrictive CSR entry selection.
With CSROR in effect:

CSRJESID=J10* CSRJOBNAME=XYZ*

are two patterns that select jobs whose JES ID begins

with 'J10' OR Job Name begins with 'XYZ'. CSROR provides

less restrictive CSR entry selection.
-Selection results from repeats of the same CSR filter

keyword are always logically ORed.

-The order of CSR filter application is:

1) CSRJOBNAME=

2) CSRJESID=

-New support for the concept of multi-table selection with

filters JOBNAME= (alias JOB=) and JESID= (alias JID=) to

allow selection by Job Name and/or JES Identification

jobname from both the RMF Monitor III ASI and CSR tables

with one keyword.

-This is a convenience feature to avoid having to code the

Job Name or JES ID selection parameters twice when the

same jobs from both tables are of interest.

-Both the ASI and CSR tables must be selected for these

multi-table selection keywords to function completely.

Otherwise, only entries from the one selected table are

filtered.
Note that most RMF III tables do not contain common

character data fields, but in this case the ASI and CSR

do.
-Example of JOBNAME= :

JOBNAME=ABC* or JOB=ABC* is equivalent to coding

ASIJOBNAME=ABC*

CSRJOBNAME=ABC*


-Example of JESID= :

JESID=JOB01000:JOB01999 or JID=JOB01000:JOB01999

is equivalent to coding

ASIJESID=JOB01000:JOB01999

CSRJESID=JOB01000:JOB01999
NOTE: If a job has ended before the selected MINTIME

intervals it will ONLY appear in the MXG ZRBCSR data set

and NOT the MXG ZRBASI data set.
-Reduced processing overhead for CSR tables.

-RMFV056* (*=I,W,E) message is no longer issued twice when

a single unpaired range value is in error.

-All invalid characters detected in a pattern are now

shown in multiple RMFV056* (*=I,W,E) messages. Before

only the first character in error was displayed. This

could result in repeated runs of ASMRMFV just to find all

the invalid characters in a pattern.

-The error message generation process has been rewritten

for improved efficiency, consistency, clarity, and

usability.
For example, the problem data area in RMFV004* and

RMFV056* messages that shows the text in error is

expanded from 24 to 63 characters. Also all length

errors are displayed in the same format.


-Added new documentation Section 26 "ASMRMFV and SAS PDB

Relationships" that explains which RMF III tables

correspond to which eventual MXG SAS datasets. If the

required RMF III table is not selected in ASMRMFV the MXG

dataset will have zero observations.
All ASMRMFV users should review this useful information.

-Old documentation Section 26 "Summary" is now Section 27.

-The PATTERR= parameter was not effective because it was

not processed until all parameters were read. This was

too late because pattern error handling must occur during

the actual parameter process as patterns are being

scanned.

-PATTERR= parameter handling now occurs immediately when

found in the JCL PARM field or SYSIN DD stream including

severity tailoring of message RMFV056* (*=I,W,E).

-The default value for PATTERR= is now PATTERR=ABEND.

Before the default was PATTERR=WARN. An incorrect


Yüklə 28,67 Mb.

Dostları ilə paylaş:
1   ...   31   32   33   34   35   36   37   38   ...   383




Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©muhaz.org 2024
rəhbərliyinə müraciət

gir | qeydiyyatdan keç
    Ana səhifə


yükləyin