Карта сайта

* copyright (C) 1984-2012 merrill consultants, dallas, texas * - старонка 145

the interval.

9. Problems with HiperBatch information in type 14/15 are fixed by

applying PTFs UY50465,UY51181,UY51182,UY54424 on top of APARs

OY30300,OY32039 and OY34754.

10.APAR OY36879, PTF UY55480 corrects a type 30 problem wherein EXCP

sections are completely missing for dynamically unallocated DD's!!

This was first noted by a tremendous drop in the EXCP counts after

maintenance, but only for TYPETASK of TSU.

11.APAR OY26507 for MVS/ESA corrects I/O connect time for VIO datasets

(by setting the value to zero, as it should have been all along!).

MXG's IOTMTODD was extremely large, and IOTMNODD was negative because

of the IBM error.

12.OY26842 (MVS/ESA only) increases the number of concurrent DDs that

can be simultaneously opened from 3723 to 10,000.

13.OY29434 (MVS/XA 2.2.0 and above) deals with destage of 3990 cache

controller data when HALT EOD command is issued.

14.OY24606 (MVS/XA 2.2.0 and above) ensures TSO SMF type 32 record is

written after TSO user is cancelled; previously last commands data

was lost.

15.OY21749 now causes the SMF dump program, IFASMFDP, to put a message

in the SYSPRINT data set if the dump program ABENDED. (Some sites

throw away their JCL and kept only the SYSPRINT, and never knew the

dump program had abended! Isn't it amazing what IBM has to do to

meet the needs of it's customers!)

16.OY32670 now causes the SMF dump program, IFASMFDP, to put a message

in the SYSPRINT data set that you tried to dump an empty SMF dataset.

17.OY32638 adds PROCSTEP to the type 30 SMF record.

18.OY25606 expands the Extra-dd field in type 30s to four bytes.

19.Newsletter NINE discussed the impact of a non-zero value for the

timezone delta, PARMTZ in SYS1.PARMLIB(PARMTZ). In MVS/ESA the delta

is set by TIMEZONE= in SYS1.PARMLIB(CLOCK00). In either case, if the

delta is non-zero, the CICS internal timestamps (STRTTIME,ENDTIME)

and DB2 internal timestamps (QWHSSTCK,QBACCBSC,QWACCESC) will be on

GMT but the SMF timestamps will be local.

20.IDRC (data compaction) on 3480 tape cartridges can be specified by

the TRTCH=COMP/NOCOMP subparameter of the DCB parameter, or can be

set by default in the DEVSUPyy member of SYS1.PARMLIB (IBM defaults

to NOCOMP). MXG 3480 tapes are always DCB=TRTCH=NOCOMP, because

IDRC is an optional hardware feature on your tape control units.

Reading an IDRC tape built with compaction on a control unit without

the IDRC hardware feature produces an I/O error with these messages:

IOS000I 410,10,NCA,02,0600,,**,,jobname


21.SYNCSORT release 3.3 truncates a VBS record with LRECL=RDW=32760!

The problem is fixed by zap EW3178-0 for that release. Without the

fix, records greater than 32756 bytes LRECL are truncated on output.

The specific occurrence of an SMF record of exactly 32760 bytes was a

type 79 subtype 1 (over 330 ASIDs active). Specifying LRECL=32760 in

the JCL of the sort did not correct the problem.

22.Some unverified comments about MVS/ESA CPU timings of Hiperspace

activity suggest that creation of a hiperspace causes CPUHPTTM to be

non-zero, but reading of data in that hiperspace causes both CPUHPTTM

and CPUTCBTM time to be recorded, because the MOVEPAGE instruction

(which is good, fast, etc., and new, and only on some hardware) does

record CPUTCBTM. Without MOVEPAGE, there will be more real CPU time

and it will be recorded in CPUHPTTM, and not in CPUTCBTM. The cost

of MOVEPAGE is on the order of one half of the cost of a page-in in

expanded memory (which has been quoted as 75 microsec for one page

but approaches 30 microsecs per page when several pages are blocked


III. SAS Notes.

1. SAS 6.06 (MVS) has been repaired, and can be safely used.

SAS 6.06 has finished its shakedown cruise, the shipyard repairs

have been made, and the October SAS Notes tape now contains a load

library with most critical, required, and recommended zaps already

installed. Sites should now request the October or later SAS Notes

Tape from SAS Technical Support and begin their testing and

migration to the new version. While there will be a SAS 6.07

version in mid-1991 with ESA exploitation, additional performance

improvements and bug fixes, there is no reason to wait. In fact, SAS

6.06 has removed constraints on program size which limited many large

site's SMF processing. With the new SMF records now created by

MVS/ESA 4.1 and the new records announced in MVS/ESA 4.2, SAS 6.06

may actually be required for BUILDPDB with MVS/ESA 4.2 next spring!

MXG now recommends testing for migration to SAS 6.06.

A PreRelease of MXG Version 8.x has NEVER BEEN REQUIRED for Execution

of MXG under MVS SAS 6.06. MXG 7.7 will execute under SAS 6.06.

What is REQUIRED is the installation of many critical ZAPS to the SAS

System. MXG Newsletter SEVENTEEN (July) listed the then-known ZAPs,

and identified several open problems. As problems were fixed, that

list grew to the following list of SAS ZAPs that are required for MXG

execution under SAS 6.06 under MVS:

Z6060135 Z6060288 Z6060529 Z6060611 Z6060640 Z6060653 Z6060872

Z6060892 Z6060916 Z6060938 Z6060946 Z6061149 Z6061220

and Z6060969 (which replaced Z6060571)

and Z6061258 (which replaced Z6060703)

and Z6061738 (which replaces Z6060652)

MXG also STRONGLY recommends that ALL ZAPs that are idenfified by SAS

as Critical, Highly Recommended, and Recommended also be installed.

Prior to the October SAS Usage Notes Tape, installing all ZAPs could

take two days, as the ZAP stream failed each time a module's IDRCOUNT

filled, requiring a link-edit of that module and a restart of the ZAP

stream. (IBM limits IDRCOUNT to 19, and SAS uses IDRs to identify the

ZAPs that have been applied to a module).

However, beginning with the October SAS Notes library, the tape now

contains the "SAS Maintenance files", which includes a load library

containing selected SAS modules with pre-applied maintenance, i.e.,

the important ZAPS have already been applied!. See Section 3.11 of

the document "MVS Version 6 SAS Notes, ZAP Libraries and Maintenance

Files", Document Number MVS6-US-1090.02, which accompanies the tape.

The following MXG-required ZAPs were not on the October SAS Notes

"Maintenance library" and will need to be applied:

Z6060916 Z6060969 Z6061258 Z6061738

While we have many sites with MXG 7.7 who are successfully executing

MXG under MVS SAS 6.06, there were seven members of MXG that had to

be changed to avoid syntax errors, and many additional members were

also changed to provide complete forward and backward compatibility

with both SAS 5.18 and SAS 6.06. We do recommend that you request

and install an MXG Version 8 PreRelease, but it is not required. The

few problems encountered using MXG 7.7 under the ZAPed SAS 6.06 have

been fixed by telephone (or by reading the Newsletter). The critical

parts of MXG 7.7 (those that build the data sets) do work under 6.06.

The biggest problem area, once these ZAPs are installed, is that when

SAS runs out of memory or disk space, strange error messages occur,

(like "no more MFEs", "data set is not sorted", "record too large").

These errors can be avoided by always executing in a 4MB or larger

region, specifying MEMSIZE=12MB (automatic, if you use MXG's CONFIG

member), and (initially) overallocate your disk space. (The 6.06 WORK

default is only CYL,(5,2)!). Overallocate, and add the SAS statement


at the end to determine how much disk space is actually required.

Does anything work well under SAS 6.06? Actually, quite a lot!

For many non-MXG applications that are not especially data or

memory intensive (the info center, and non-programmers), there

is a lot of SAS 6.06 that does work real well, especially the

SAS/ASSIST and the display manager. These new tools that make SAS

efficient in the hands of non-programmers have received positive

feedback, especially from sites that had never used SAS before.

The portions of SAS 6.06 that had already been sailing in the PC

versions 6.02 and 6.03 did port over to MVS with fewer problems.

It was only the processing of large files with large MXG programs

with large memory requirements that caused most of the repairs.

The following ZAPs are included in the preceding list, but they have

not been described in previous MXG newsletters.

a. ZAPs Z6060135, Z6061149 and Z6061220 are required, and may

resolve Usage Note 1000 errors, which include "Data is not

Sorted", "Record in buffer is too long", User 0016 ABENDs from

SORT program, and/or E15 or E35 SORT exit error, depending on

SORT program used. The real cause of most (perhaps all) of these

error messages was that the SAS library being created (WORK, PDB,

etc.) ran out of space, but SAS 6.06 mis-recognized the condition

and produced an incorrect error message.

Note added 1996: The E35 SORT exit error message was not fixed

until SAS 6.08 at TS410 (or ZAP Z6088203 for TS407 was applied).

b. ZAP Z6060916 is absolutely required. Without this zap, the

%VMXGSUM macro (used in ASUM.... and TRND.... members for

trending/summaries) will generate incorrect (but error-free) SAS

code and data sets built with %VMXGSUM will be wrong.

c. ZAP Z6060892 is required if you have a DASD Cache Controller 3880

or 3990 device. Formatting a 500 Cyl work file was done with a

single CCW chain which took an enormous amount of SQA storage,

and the "Missing Interrupt Handler" time delta was not long

enough to handle the transmission of the CCW chain TO the Cache

Controller, let alone to wait for it to complete. This ZAP

breaks down the formatting of SAS 6.06 data libraries into 5

cylinder chunks to avoid the problem.

d. SAS ZAP Z6061465 corrects SAS failure to handle broken VBS

segment if the bad segment is the last record on a data set.

Instead of deleting the bad VBS segment, SAS failed, either with

a OC1 or by permanently entering the wait state. This ZAP

correctly deletes the defective VBS segment, and continues

processing the input data set.

e. PROC CHART against a data set with zero observations erroneously

sets a condition code of 8 and a scurrilous error message that

won't be corrected until SAS 6.07, according to Usage Note


f. Overriding JCL DD statements must be in exactly the same order

that those DD statements appear in the SAS 6.06 JCL procedure.

The SAS606 order is


g. DATETIME21.2 of '06NOV90:07:30:50' prints '06NOV90:07:30.491.0',

and 30:51 prints as 30:501.0. SAS Usage Note 793 discusses this

generic problem with fractional time values, but no ZAP exists.

h. PROC MEANS was changed in 6.06, and now operates only on a

maximum of 400 variables. If a new data set is to be built from a

data set of over 400 variables with PROC MEANS OUTPUT, the

created dataset will be corrupted, as it will contain only the

first 400 variables, and NO ERROR MESSAGE OR CONDITION CODE is

set by SAS 6.06! MXG does not have a PROC MEANS with OUTPUT on

any data set of over 400 variables, but this new design "feature"

is disconcerting, considering SAS's pre 6.06 philosophy to not

restrict users with capricious limitations! SAS Compatibility

Note Number 779 discusses this restriction, which will be removed

in SAS 6.07.

2. SAS options that are now required for MXG execution.

Some Options are now MANDATORY for successful MXG execution which might

have been optional in the past.

MANDATORY OPTIONS under both SAS Versions:


MANDATORY OPTIONS under SAS Version 5.18:

MWORK=28000 GEN=0

MANDATORY OPTIONS under SAS Version 6.06:


RECOMMENDED Options under either SAS Version:



For SAS Version 5.18, MACRO and MWORK=28000 must be specified on the

EXEC statement, while all other mandatory/recommended options can be

specified on an OPTIONS statement before your %INCLUDE statements:

a.) //stepname EXEC SAS,OPTIONS='MACRO MWORK=28000'








b.) New member SASOPTV5 has been added to eliminate the need for

typing all the above options, and can be used instead each

time you execute MXG under SAS 5.18:




... the rest of your program ...

For SAS Version 6.06+, options can be supplied via the CONFIG DDname in

your JCL, or with an OPTIONS statement. PreRelease member CONFIG is a

changed copy of the SAS-supplied BATCHXA config member, with these new

options specified for MXG execution. (Note MWORK= and GEN= don't exist

in SAS 6.06):







3. Format libraries under MVS SAS 6.06 or 5.18.

The MXG-built "SASLIB" formats are built by the first step of

JCLTEST (for SAS 5.18) or by the first step of JCLTEST6 (for SAS

6.06). Under SAS Version 5.18, formats are members of a PDS and

referenced by the SASLIB DDname, and require SPACE=(CYL,(3,1,99)).

Under SAS Version 6.06, formats are members of a SAS data library,

referenced by the LIBRARY DDname, and require SPACE=(CYL,(1,1)).

Note the absence of the third (PDS directory blocks) for SAS 6.06.
2014-07-19 18:44
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • © sanaalar.ru
    Образовательные документы для студентов.