.RU
Карта сайта

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


bit 22 MAXTASK 64 Maximum Task condition delay

bit 23 SHRTSTOR 64 Short on Storage condition delay

Comment: By deleting PAGEINS from CICS Transaction records, IBM has

substantially reduced the cost of running the CICS Monitor Facility,

since capture of paging activity was a significant contributor to

of overhead of monitoring CICS. IBM now suggests that overhead due

to the CICS monitor is on the order of 5-7%, but that has not yet

been verified by an MXG user.

CICSTRAN Fields changed by CICS 3.1.1.

Labels for STORHWMK, SCGETCNT, and PAGESECS now include "Below 16MB"

and PROGSTOR includes "Above & Below 16MB" to contrast with the new

storage variables added below.

CICSTRAN Fields changed by CICS 3.1.1.

MXG Variable /* CMODNAME */

LUNAME ='LOGICAL*UNIT*NAME'

Logical unit name. VTAM logical unit name (if available) of

the terminal associated with this transation. This field is

nulls if the task is not associated with a terminal.

PAGESECH='MEMORY*PAGESECS*(PER TCB) ABOVE 16MB' /* SCUSRSTGH*/

Storage occupancy pageseconds of the user-task above the

16MB line.

PC24BHWM='PROGRAM*STORAGE*BELOW 16MB ' /* PC24BHWM */

Maximum amount (high-water-mark) of program storage in use

by the user task below the 16MB line. This variable is the

subset of PROGSTOR that resides below the 16MB line. The

program storage currently in use below the 16MB line is

incremented at LOAD, LINK, and XCTL events by the size

(in bytes) of the referenced program, and is decremented at

RELEASE, or RETURN events, provided that the referenced

program resides below the line. Note: On an XCTL event the

program storage currently in use below the 16MB line can be

additionally decremented by the size of the program issuing

the XCTL, provided that this program resided below the line.

RTYPE ='RECORD*TYPE ' /* RTYPE */

Performance record type (rightmost bytes), decoded by

the $MG110RT. format. Values are:

' C'='C:TERMINAL CONVERSE'

' D'='D:USER EMP DELIVER REQUEST'

' T'='T:TASK TERMINATION'

' MT'='MT:SEMI-PERMANENT MIRROR SUSPEND'

SCGETCNH='USER STORAGE*GM REQUESTS*ABOVE 16MB ' /* SCUGETCTH*/

Count of the number of user storage GETMAIN requests

issued by the user task for storage above the 16MB line.

STORHWMH='USER STORAGE*MAX (HWM)*ABOVE 16MB ' /* SCUSRHWMH*/

Maximum amount (high water mark) of user-storage allocated

to the user task above the 16MB line.

TCLASS ='TRANSACTION*CLASS*AT CREATE'

Transaction priority at task creation (rightmost byte of

this four-byte variable).

TCSTG ='AMOUNT OF*TERMINAL*STORAGE ' /* TCSTG */

Amount of terminal storage (TIOA) allocated to the terminal

associsted with this user task, if applicable. This value

is set at task attach and after a terminal session converse.

TRANPRI ='TRANSACTION*PRIORITY*AT CREATE'

Transaction priority at task creation (rightmost byte of

this four-byte variable).

WTDISPCN='USERTASK*RE-DISPATCHES ' /*DISPWTT */

Count of number of times when the user-task waited for

re-dispatch.

WTDISPTM='USERTASK*RE-DISPATCH*WAIT TIME '

Elapsed time for which the user-task waited for re-dispatch.

This is the aggregate of the wait times between each event

completion and the user-task re-dispatch. Note: This does

not include the time spent waiting for first dispatch.

WTEXWTCN='EXCEPTION*CONDITIONS '

Count of the number of exceptional conditions that have

occurred for this task.

WTEXWTTM='EXCEPTION*CONDITION*WAIT TIME ' /*EXWTTIME */

Total elapsed time for which the user waited on exceptional

conditions. Will be null if EXCEPTION CLASS=OFF specified.

WTTDIOCN='VSAM TRANSIENT*DATA IO*WAITS '

Count of the number of times when the user waited for

VSAM transient data I/O.

WTTDIOTM='VSAM TRANSIENT*DATA IO*WAIT TIME ' /*TDIOWTT */

Total elapsed time for which the user waited for VSAM

transient data I/O.

d. New CICS 3.1.1 Statistics Data Sets descriptions.

There are 47 new CIC..... data sets created from the new subtype 2 data.

Those 47 new data sets contain 1465 new variables, which would take 32

pages just to list their names! That list is contained in DOCVER08 and

DOCVER in the MXG 8.2 PreRelease, and field descriptions are found in

IBM's "CICS/ESA 3.1 Performance Guide". The forty seven data sets are:

MXG STID DFH Description of Data Set Symbolic MXG

Dataset ... IBM Exit

Name DSECT Name Name

CICAUSS 22 AUS Autoinstalled Terminal Unsolicited STIAUSS AUS

CICAUTO 24 A04 Autoinstall Global STIAUTO AUT

CICBTAM 82 A06 Terminal Control BTAM STIBTAM BTA

CICCONMR 76 A20 ISC/IRC Mode Entry Specific STICONMR CO3

CICCONMT 77 A20 ISC/IRC Mode Entry Totals STICONMT CO4

CICCONSR 52 A14 ISC/IRC System Entry Specific STICONSR CO1

CICCONST 53 A14 ISC/IRC System Entry Totals STICONST CO2

CICDBUSS 28 DBU DBCTL Global Unsolicited STIDBUSS DBU

CICDLIR 70 A18 DL/I Specific STIDLIR DL1

CICDLIT 71 A18 DL/I Totals STIDLIT DL2

CICDMG 15 DMG Domain Manager Global STIDMG DMG

CICDMR 13 DMR Domain Manager Specific STIDMR DMR

CICDQG 45 A11 TDQUEUE Transient Data Global STITDQG DQG

CICDQR 43 A10 TDQUEUE Transient Data Specific STITDQR DQR

CICDQT 44 A10 TDQUEUE Transient Data Totals STITDQT DQT

CICDS 57 DSG Dispatcher Domain, CPU each TCB STIDS DS

CICDTB 33 A05 Dynamic Transaction Backout Global STIDTB DTB

CICFCR 67 A17 File Control Specific STIFCR FCR

CICFCT 68 A17 File Control Totals STIFCT FCT

CICIRCB 75 A19 IRC Batch Global STIIRCB IRC

CICJCR 49 A13 Journal Control Specific STIJCR JCR

CICLDG 27 LDG Loader Domain for Program Global STILDG LDG

CICLDR 25 LDR Loader Domain for Program Specific STILDR LDR

CICLDT 26 LDR Loader Domain for Program Totals STILDT LDT

CICLSRFR 40 A09 LSRPOOL File stats each File STILSRFR LS3

CICLSRFT 41 A09 LSRPOOL File stats Totals STILSRFT LS4

CICLSRR 37 A08 LSRPOOL Pool stats each LSR pool STILSRR LS1

CICLSRT 38 A08 LSRPOOL Pool stats Totals STILSRT LS2

CICM 81 MNG Monitor Domain Global STIM M

CICSDG 90 SDG System Dump Global STISDG SDG

CICSDR 88 SDR System Dump Specific STISDR SDR

CICSMD 7 SMD Storage Manager Domain Subpool STISMD SMD

CICSMSDA 9 SMS Storage Manager DSA and EDSA STISMDSA SMS

CICSMT 8 SMT Storage Manager Task Subpool STISMT SMT

CICST 66 STG Statistics Domain Global STIST ST

CICTC 3 A01 Task Control Global STITC TC

CICTCLR 58 A15 TCLASS Transaction Class Specific STITCLR TC1

CICTCLT 59 A15 TCLASS Transaction Class Totals STITCLT TC2

CICTCR 34 A06 Terminal Control Specific STITCR TCR

CICTCT 35 A06 Terminal Control Totals STITCT TCT

CICTDG 87 TDG Transaction Dump Global STIDTG TDG

CICTDR 85 TDR Transaction Dump Specific STITDR TDR

CICTM 63 A16 Table Manager Global STITM TM

CICTSQ 48 A12 TSQUEUE Temporary Storage Global STITSQ TSQ

CICTSR 4 A02 Transaction Statistics Specific STITSR TSR

CICTST 5 A02 Transaction Statistics Totals STITST TST

CICVT 21 A03 VTAM Global STIVT VT

e. Observed CICS 2.1 CICSYSTM and MONITASK datasets CPU timings.

This CICS note applies to CICS 2.1 and earlier, and not the new CICS 3.1

described above (which does not contain the CICSYSTM data set). The CPU

measures in IBM's CICSYSTM dataset should match this schematic:

CPUTCBTM=ADSPTIME SRB

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

MAINCPTM SUBTCPTM

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

KCCPUTM USRCPUTM OSWTCPTM

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

JCCPUTM TCCPUTM TASKCPTM

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

"CICS" "APPL"

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

The CICSYSTM fields contained in IBM's record are the ADSPTIME, KCCPUTM,

USRCPUTM (and its JCCPUTM and TCCPUTM components), and the SRBCPUTM.

MXG stores ADSPTIME in CPUTCBTM, and calculates SUBTCPTM, the subtask

CPU time, (which is also stored in OSWTCPTM, its older name).

One site found numerous negative values for SUBTCPTM, with the largest

value of -1.47 seconds. That 900 second interval had ADSPTIME of 426.72,

but the MAINCPTM sum of KCCPUTM (37.18) and USRCPUTM (391.01) of 428.19

was 1.47 seconds greater than ADSPTIME! Both the ADSPTIME and the sum

of MAINCPTM are suspect, because the CICS region's RMF TCB was 414.32,

or CICS recorded 14 seconds more than RMF recorded! (The type 110 SRB

CPU of 25.82 was slightly less than the RMF SRB time of 27.82.) CICSYSTM

data from a second unrelated site showed the same pattern; the CICS

recorded ADSPTIME was less than the sum of KCCPUTM and USRCPUTM, causing

SUBTCPTM to be negative, and RMF CPUTCTBM was also less than the

ADSPTIME. Investigation is still open.

Landmark sites MONISYST noted a different problem with Landmark 7.1, but

rather than a data error, the problem was MXG's lack of understanding of

what's captured. Landmark fields KCCPUTM, JCCPUTM, TCCPUTM, TASKCPTM,

and OSWTCPTM include both TCB and SRB time. Landmark also captures two

other TCB+SRB CPU measures, IRCPUTM and VSCPUTM. Landmark's schematic:

CPUTCBTM SRB

--------------------------------------------------------- + ---

KCCPUTM JCCPUTM TCCPUTM TASKCPTM OSWTCPTM IRCPUTM VSCPUTM

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

Validation of any CICS monitor's CPU time is non trivial, since CPU time

for startup/shutdown of the region is recorded in the first and last RMF

interval CPU time and in the type 30 step termination CPU time, but it

is not capturable in the CICS monitor's CICSYSTM/MONITASK records. It is

possible the CICSYSTM measures noted above are not real errors; perhaps

the CPU time occurred but was simply being assigned to a wrong interval?

Further investigation is under consideration, and ideas are welcome!

6. SAS 6.06.01 Issues and MXG recommendations.

************************************************************************

* *

* MXG's Official Position with regard to SAS 6.06.01, July 10, 1990: *

* *

* A new ship's keel is laid 3 years before the ship is launched into *

* the water. Two years later, the ship is commissioned and is sent *

* out on its "shakedown cruise". The ship floats, makes way under *

* its own power, and gets you there, but imperfections are discovered.*

* After the shakedown cruise, the shipyard fixes the things that are *

* broken, and a year or so later the ship is placed in full service. *

* *

* SAS 6.06.01 is currently on its "shake-down cruise". *

* *

* SAS Institute ZAPs are required before MXG can be safely executed *

* under SAS 6.06. Additional problems that cannot be fixed by zap *

* will not be available until SAS 6.08 is released (in mid-1991). *

* *

* In addition, source modifications to MXG Version 7.7 may be needed *

* to circumvent some incompatibilities between 5.18 and 6.06. *

* MXG 8.2 contains these source changes, which are identified below. *

* *

* Initial performance measurements for MXG execution under SAS 6.06 *

* show significantly more CPU time is required than under SAS 5.18. *

* Both data-intensive sequential processing and compiler-intensive *

* processing recorded more CPU time, although in some cases the I/O *

* counts and elapsed run time were slightly reduced. Further testing *

* of new SAS options and investigation by SAS Institute is ongoing. *

* *

* Some MXG sites may actually require SAS 6.06. *

* *

* Sites which have encountered the SAS "344 Compiler Limit Exceeded" *

* condition will find that that limit (as well as other constraints) *

* have been eliminated in SAS 6.06. *

* The new support for the Cray COS operating system requires the new *

* $ASCII. format, and the planned new support for DEC VMS data will *

* require both $ASCII. and VAXRB. formats that are only in SAS 6.06. *

* *

* The ZAPs listed below are required because MXG fails without them. *

* Additional 6.06 problems have been reported and fixed by SAS ZAPs. *

* These ZAPs can be downloaded from the Institute's "Online Customer *

* Support Facility". Alternatively, SAS Institute will make available*

* (in mid-July), the "July SAS 6.06 Usage Notes Tape". That tape will *

* contain these Required, Highly Recommended, Recommended, and Special*

* Consideration categories of ZAPs to be installed on SAS 6.06. *

* *

* SAS Institute asks that you request the "July Usage Notes Tape" in *

* writing, addressed to their SAS Distribution Center, and that you *

* indicate the operating system (OS or CMS) and tape (reel/cart) type.*

* The procedures for downloading ZAPs and installing maintenance are *

* discussed in SAS Technical Bulletin U-112, packaged with SAS 6.06. *

* *

* In summary, get and install the "July Usage Notes Tape" before you *

* begin testing MXG under SAS 6.06. *

* *

* SAS Version 6 is a major re-design, and will require planning and *

* testing of your critical SAS applications before their migration. *

* *

* There are many new features and benefits in SAS 6.06 that do work. *

* Before too long, all will be smooth sailing with following seas! *

* *

************************************************************************

a. SAS 6.06 ERROR Conditions requiring ZAPS to be installed.

1. ZAP Z6060611 required.

Fixes a SAS logic error that caused the MVS Initiator to ABEND

because LSQA had filled because SAS had opened SOURCLIB over 2000

times and filled LSQA with DEBs! This error was uncovered only

because IMPLMAC was (incorrectly) enabled when BUILDPDB ran!

2. ZAP Z6060640 required.

A STOPOVER condition executed when INPUT STATEMENT EXCEEDED RECORD
2014-07-19 18:44
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • Контрольная работа
  • © sanaalar.ru
    Образовательные документы для студентов.