Yola



Mainframe Operations Manual

Contents

1 Hardware Configuration 6

1.1 Processor Configuration 6

1.1.1 Stockley Park 6

1.1.2 Greenford 6

1.2 Hardware Configuration Definition 7

1.2.1 HCD - What Is It? 7

1.2.2 How To Check On The Current Status 7

1.2.3 Contact 7

1.3 DASD Configuration 8

1.3.1 DASD Configuration Diagrams 8

1.4 Hardware Management Consoles (HMC) 9

1.4.1 Introduction 9

1.4.2 Hardware Management Console Workplace Panel 9

1.4.3 Users Defined to the HMC 9

2 Power On Procedures 10

2.1 Processor Complex - IBM/2064 10

2.2 3174 Control Unit 11

3 Power Off Procedures 12

3.1 Schedule power-off 12

3.2 Emergency Power-off (Processor) 13

3.3 Emergency Power-off (Peripherals) 14

4 Operating The IBM 2064 Processor 15

4.1 Power On/Off The Processor 15

4.1.1 Power On (from the Groups Work Area) 15

4.1.2 Power Off (from the Groups Work Area) 15

4.2 Activate/De-Activate A Partition 16

4.2.1 Activate A Partition 16

4.2.2 Deactivate A Partition 16

4.3 IPL A Partition 17

4.3.1 To Initiate The IPL 17

4.3.2 Loading Services 17

4.4 Display Hardware Messages 18

4.5 Terminate Service Mode 19

5 Change Defined Capacity 20

5.1 Steps to Acquire Additional CPU Resources 20

5.1.1 General Information 20

5.1.2 Alert on Soft Capping 20

5.1.3 Procedure to Change Defined Capacity 20

5.1.4 Vary Additional CPU Online 21

5.2 Change Processor Weights of a LPAR 22

5.3 Check Whether LPAR Is Being Soft Capped 23

5.3.1 Message from the SOLVE Monitor 23

5.3.2 Started Task RMFM3B 23

5.4 To Change/Remove the Soft Cap Value 24

6 Problem Determination 25

6.1 Hardware Error 25

6.1.1 Processor Failure 25

6.1.2 Device Failure 25

6.1.3 MVS Console Failure 25

6.1.3.1 To Use the HMC as the MVS Console 25

6.2 Software Error 27

6.2.1 If TSO Is Available 27

6.2.2 If TSO Is Not Available 27

6.3 Standalone Dump 28

6.3.1 Capture StandAlone Dump 28

7 Production Sysplex 30

7.1 IPL System Into A Sysplex 30

7.1.1 IPL 1st System Into Sysplex (For The First Time) 30

7.1.2 IPL Other Systems Into The Sysplex (For The First Time) 30

7.1.3 Subsequent IPL Systems Into The Sysplex 30

7.1.4 Problem With CTCs 30

7.1.5 Re-Joining Sysplex Without Prior Removal 31

7.2 Global Resource Serialisation (GRS) 32

7.2.1 General Information 32

7.2.2 Message 32

7.2.3 Useful GRS commands 32

7.3 Removing A System From Sysplex 33

7.4 Sysplex Commands 34

7.5 Couple Datasets 35

7.6 LOGREC Recording (no longer required) 36

7.6.1 To Switch LOGREC To DASD Recording 36

7.6.2 To Switch LOGREC Back To Using Coupling Facility 36

7.6.3 Display Current Recording Medium of LOGREC 36

7.7 Sysplex Timer Failure 37

7.8 Loss of Primary Couple Dataset When An Alternate Exists 38

7.9 Loss of Primary Couple Dataset When No Alternate Exists 39

7.10 Loss of A System In Sysplex 40

7.10.1 Loss Of System 40

7.10.1.1 Status Update Missing Condition Occurs (message IXC402D) :- 40

7.10.1.2 Power Loss to Disks 40

7.10.1.2.1 If system is not in sysplex 41

7.10.1.2.2 If system is in sysplex 41

7.10.2 System Reload 41

7.11 Couple Datasets Placement 42

7.11.1 Stockley Park 42

7.11.2 Greenford 43

7.12 Power Down of Quadrants 2 & 3 44

7.12.1 General Information 44

7.13 Power Down of Quadrants 1 & 4 45

7.13.1 General Information 45

7.13.2 Actions to terminate sysplex processing for the power down systems 45

7.13.3 Switch Couple Datasets 45

7.13.3.1 Switch XCF couple dataset 45

7.13.3.2 Switch CFRM couple datasets 46

7.13.3.3 Switch LOGR couple dataset 46

7.13.3.4 Switch WLM couple datasets 46

7.13.4 Close LPARs. 47

7.13.5 Final steps 47

7.13.6 Check status of couple datasets 47

7.14 Power Up of Quadrants 1 & 4 49

7.14.1 General Information 49

7.14.2 Actions to re-establish sysplex processing for all systems 49

7.14.2.1 Activate the Coupling Facility 49

7.14.2.2 Vary sysplex DASD online 49

7.14.2.3 Switch XCF couple dataset 50

7.14.2.4 Switch CFRM couple datasets 50

7.14.2.5 Switch LOGR couple dataset 50

7.14.2.6 Switch WLM couple datasets 51

7.14.2.7 Check the status of the couple datasets 51

7.14.2.8 Reload systems 51

7.15 Switching Systems to Greenford 52

7.15.1 Close systems at Stockley Park 52

7.15.2 IPL systems at Greenford 52

7.16 Switching Systems Back From Greenford 53

7.16.1 Close down at Greenford 53

7.16.2 Bring systems up at Stockley Park 53

7.17 Removing The Coupling Facility 54

7.17.1 General Information 54

7.17.1.1 Deactivate CF01 54

7.17.1.1.1 Move structures away from CF01 54

7.17.1.1.2 Close down CF01 55

7.17.1.2 Deactivate CF02 55

7.17.1.2.1 Move structures away from CF02 55

7.17.1.2.2 Close down CF02 55

7.18 Error Messages Expected During Power Down 56

7.18.1 Loss of couple dataset 56

7.18.2 Loss of a sysplex timer 56

7.19 Workload Manager (WLM) 57

7.19.1 WLM Policies 57

7.19.2 Policy Management 58

7.19.2.1 Default Policy Schedule 58

7.19.2.2 Special Policy Schedule 58

7.19.2.2.1 Activate SHADOW Policy 58

7.19.2.2.2 Deactivate SHADOW Policy 58

7.19.3 Change WLM Policy(via TSO) 59

7.19.4 Workload Manager Concepts 60

7.19.5 Useful WLM Commands 61

7.20 Tape Sharing 63

7.20.1 General Information 63

7.20.2 To deactivate tape sharing 63

7.20.3 To activate tape sharing 63

7.20.4 To display current devices in automatic tape sharing 63

7.21 Pathin & Pathout Device Number 64

8 Development Sysplex (Differences to Production Sysplex) 65

8.1 Couple dataset placement 65

8.2 Coupling Facility 65

8.3 Pathin and pathout device number 65

8.4 Fallback couple datasets 65

8.5 Power down/up of Quadrant 1 & 4 65

9 Sysplex Disk Placement (Production) 66

10 Sysplex Structure Diagram (Production) 67

11 Sysplex Disk Placement (Development) 68

12 Sysplex Structure Diagram (Development) 69

1. Hardware Configuration

1. Processor Configuration

1. Stockley Park

There are 2 processors located at Stockley Park :-

• IBM 2064/2C6

• IBM 2064/2C6

All the processors are now residing in a Quadrant 1 which is dual powered.

2. Greenford

At Greenford, there are 2 back-up processors which can be treated as warm stand-by processors. In case of power down at Stockley Park or in a disaster recovery situation, these processors are brought into operation.

2. Hardware Configuration Definition

1. HCD - What Is It?

Hardware Configuration Dialogue is a method for implementing changes to the IOCDS & MVSGEN equivalent, without an IPL or IML. It will not completely eliminate them, as sooner or later an IML will be required to clear up HSA (Hardware Service Area).

It is invoked from a TSO terminal, and devices can be added, removed or reconfigured. Once this has been done on all partitions affected, the configuration is activated by the ACTIVATE command, either from TSO or the console.

2. How To Check On The Current Status

D IOS,CONFIG

This will generate display as follow :-

IOS506I 16.49.47 I/O CONFIG DATA 894

ACTIVE IODF DATA SET = SYS0.IODF04 DEVPLEX

S ==> PRDPLEX

==> TESTPLEX

==>

==>

PF3 TO QUIT ENTER TO REDISPLAY PANEL

➢ Select the Sysplex schedule required

COMMAND INPUT ===> Row 1 to 24 of 24

WLM POLICY SCHEDULE PRDPLEX

PF3 TO UPDATE/EXIT, PF4 TO RESET TO DEFAULT

TIME MONDAY TUESDAY WED-DAY THURSDAY FRIDAY SATURDAY SUNDAY

00:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

01:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

02:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

03:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

04:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

05:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

06:00 BASE BASE BASE BASE BASE BASE BASE

07:00 BASE BASE BASE BASE BASE BASE BASE

08:00 BASE BASE BASE BASE BASE BASE BASE

09:00 BASE BASE BASE BASE BASE BASE BASE

10:00 BASE BASE BASE BASE BASE BASE BASE

11:00 BASE BASE BASE BASE BASE BASE BASE

12:00 BASE BASE BASE BASE BASE BASE BASE

13:00 BASE BASE BASE BASE BASE BASE BASE

14:00 BASE BASE BASE BASE BASE BASE BASE

15:00 BASE BASE BASE BASE BASE BASE BASE

16:00 BASE BASE BASE BASE BASE BASE BASE

17:00 BASE BASE BASE BASE BASE BASE BASE

18:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

19:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

20:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

21:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

22:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

23:00 NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT NIGHT

➢ Over type any policy name to change the schedule. PF4 will always return to the default schedule.

4. Workload Manager Concepts

Concept 1

The Workload Manager (WLM) is NOT a LPAR workload manager, WLM manages the Sysplex.

Concept 2

A change to the WLM policy is effective across all LPARs defined to the sysplex.

Concept 3

(A M&S constraint), work assigned to the following Service Classes

MONITORS

ONL_HIGH

ONL_VHGH

SRV_HIGH

SRV_STD

STC_HIGH

STC_STD

will not be pre-empted by any other workload.

Concept 4

Service class FLYING. This is a special facility for providing a boost to a specific job. No work is automatically scheduled to this service class and is only selected by operator control.

The selected job will run at a significantly high dispatch priority for approximately 0.5 second CPU usage it will then drop to BAT_STD.

Concept 5

The service class ONL_SDBB is specifically constrained across the sysplex. The constraint is primarily for CM21 unfortunately the constraint specification includes all services where SDBB is running.

This constraining facility is utilised in the policy SHADOW set up for use by operations when a request to reduce SDBB system usage by 25% is received.

Concept 6

The service class GROUNDED is a discretionary definition. Any work placed in this service class will only consume spare resources.

Concept 7

The service class TSO_RCVY is meant to be use for exceptional access requirements. The first period is set to execute at a level equivalent to the online services, slowly falling to a level above normal TSO.

TSO is transaction based, this is the time between entering the command and receiving the response to the command, consequently 90% of this service class usage will receive exceptional response.

The only way into this service class is by operator command. A user must not stay in this class for long, it is define for emergency use only.

Concept 8

Service class BAT_SMLL. Beware of this service class. It is defined to support initiator classes A and 1.

Class A is the default class if no class is specified in the JCL and TIME=(0002) specified (2 minutes CPU).

Class 1 is for quick jobs, also with TIME=(0002) specified (2 minutes CPU).

BAT_SMLL will fall quickly from a high resource consumption definition and will be penalised if it does not complete in time.

5. Useful WLM Commands

➢ Assigns the requested address space with a new service class. This will also resume quiesced work.

E jjjjjjjj,SRVCLASS=nnnnnnnn

(where jjjjjjjj is jobname & nnnnnnnn is service class)

➢ Set the requested address space with the lowest possible performance

characteristics. It will not stop work!

E jjjjjjjj,QUIESCE

➢ Reclassify a reset or quiesced address space with the service class defined in the

active policy.

E jjjjjjjj,RESUME

20. Tape Sharing

1. General Information

All systems in the Sysplex by default will be using ATS Star, unlike it’s predecessor (IEAUTOS), this no longer uses the coupling facility, purely XCF.

2. To deactivate tape sharing

Issue the following command on any active sysplex console, where mmmm-nnnn is the

address range of the tape devices :-

RO *ALL,V mmmm-nnnn,OFFLINE ( vary devices offline

RO *ALL,V mmmm-nnnn,AS,OFF ( stop automatic tape sharing

3. To activate tape sharing

Issue the following command on any active sysplex console, where mmmm-nnnn is the

address range of tape devices :-

RO *ALL,V mmmm-nnnn,OFFLINE ( vary non-sharing devices

offline

RO *ALL,V mmmm-nnnn,AS,ON ( start automatic tape sharing

RO *ALL,V mmmm-nnnn,ONLINE ( vary sharable tape devices

online

4. To display current devices in automatic tape sharing

Issue system command

D U,,AS,100

21. Pathin & Pathout Device Number

The following table show the device number associated with the PATHIN and PATHOUT for each of the production service :-

|SYSTEM |PATHIN DEVICE NUMBER |PATHOUT DEVICE NUMBER |

| | | |

|CM11 |F224, FC24, F225, FC25 |F226, FC26, F227, FC27 |

| | | |

|CM11BU |F23C, FC3C, F23D, FC3D |F23E, FC3E, F23F, FC3F |

| | | |

|CM12 |F218, FC18, F219, FC19 |F21A, FC1A, F21B, FC1B |

| | | |

|CM12BU |F2B4, FCB4, F2B5, FCB5 |F2B6, FCB6, F2B7, FCB7 |

| | | |

|CM21 |F228, FC28, F229, FC29 |F22A, FC2A, F22B, FC2B |

| | | |

|CM21BU |F22C, FC2C, F22, FC2D |F22E, FC2E, F22F, FC2F |

| | | |

|HC03 |F220, FC20, F221, FC21 |F222, FC22, F223, FC23 |

| | | |

|HC03BU |F230, FC30, F231, FC31 |F232, FC32, F233, FC33 |

| | | |

|SP02 |F21C, FC1C, F21D, FC1D |F21E, FC1E, F21F, FC1F |

| | | |

|SP02BU |F234, FC34, F235, FC35 |F236, FC36, F237, FC37 |

| | | |

|SS02 |F204, FC04, F205, FC05 |F206, FC06, F207, FC07 |

| | | |

|SS02BU |F238, FC38, F239, FC39 |F23A, FC3A, F23B, FC3B |

| | | |

|CMC1 |F20C, FC0C, F20D, FC0D |F20E, FC0E, F20F, FC0F |

| | | |

|CMC2 |F2B0, FCB0, F2B1, FCB1 |F2B2, FCB2, F2B3, FCB3 |

| | | |

|CMC2BU |F2B8, FCB8, F2B9, FCB9 |F2BA, FCBA, F2BB, FCBB |

8. Development Sysplex (Differences to Production Sysplex)

Development sysplex does not share the same sysplex as production. It shares the same concept but not the same environment as the production sysplex. Anything applies to the production sysplex can also be applied to the development sysplex.

There are only 5 major differences between production and development sysplex :-

1. Couple dataset placement

See Chapter 11 for details.

2. Coupling Facility

See Chapter 12 for details.

3. Pathin and pathout device number

|System |Pathin Device Number |Pathout Device Number |

|HC01 |F210, FC10 |F212, FC12 |

|SP01 |F214, FC14 |F216, FC16 |

|QPP1 |F200, FC00 |F202, FC02 |

4. Fallback couple datasets

There are no fallback couple datasets for the development sysplex.

5. Power down/up of Quadrant 1 & 4

Only the power down of Quadrants 1 & 4 affect the development sysplex. In this case,

both development services have to be closed down.

Power up of Quadrant 1 & 4 will follow the same procedure as for production sysplex.

9. Sysplex Disk Placement (Production)

STOCKLEY PARK

QUADRANT 1 QUADRANT 2

PPRC'ed PPRC'ed

Only used when running at Greenford

10. Sysplex Structure Diagram (Production)

STOCKLEY PARK

2064/DC4A 2064/DC6A

11. Sysplex Disk Placement (Development)

Stockley Park

12. Sysplex Structure Diagram (Development)

STOCKLEY PARK

2064/DC4A 2064/DC6A

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

SYXQ2L (6769)

SYS1.PRDPLEX.LOGR. CDSQ2P

This disk is PPRD'ed to Greenford

SYXQ2S (676A)

SYS1.PRDPLEX.CFRM.FCDSQ2S

SYS1.PRDPLEX.XCF.FCDSQ2S

SYS1.PRDPLEX.WLM.FCDSQ2S

SYXQ1S (4B2F)

SYS1.PRDPLEX.CFRM.FCDSQ1S

SYS1.PRDPLEX.XCF.FCDSQ1S

SYS1.PRDPLEX.WLM.FCDSQ1S

SYXQ1L (4B2D)

SYS1.PRDPLEX.LOGR.CDSQ1S

This disk is PPRC'ed to Greenford

SYXQ1P (4B2E)

SYS1.PRDPLEX.CFRM.CDSQ1P

SYS1.PRDPLEX.XCF.CDSQ1S

SYS1.PRDPLEX.WLM.CDSQ1P

SYS1.PRDPLEX.LOGR.FCDSQ1S

SYXQ2P (676B)

SYS1.PRDPLEX.CFRM.CDSQ2S

SYS1.PRDPLEX.XCF.CDSQ2P

SYS1.PRDPLEX.WLM.CDSQ2S

SYS1.PRDPLEX.LOGR.FCDSQ2S

LOGR01 (4B42)

SYS4.SYSPLEX.LOGREC.*

SYXG1S (5B42)

(only use in the Greenford switch)

SYS1.PRDPLEX.XCF.CDS02

SYS1.PRDPLEX.LOGR.CDS02

SYS1.PRDPLEX.WLM.CDS02

SYS1.PRDPLEX.CFRM.CDS02

SYXG1P (5B41)

(only use in the Greenford switch)

SYS1.PRDPLEX.XCF.CDS01

SYS1.PRDPLEX.LOGR.CDS01

SYS1.PRDPLEX.WLM.CDS01

SYS1.PRDPLEX.CFRM.CDS01

PPRC of SYXQ2L at Stockley Park

SYS1.PRDPLEX.LOGR.CDSQ2P

PPRC of SYXQ1L at Stockley Park

SYS1.PRDPLEX.LOGR.CDSQ1S

SYXQ2L (6769)

SYS1.PRDPLEX.LOGR.CDSQ2P

SYXG1S (5B42)

SYS1.PRDPLEX.XCF.CDS02

SYS1.PRDPLEX.LOGR.CDS02

SYS1.PRDPLEX.WLM.CDS02

SYXG1P (5B41)

SYS1.PRDPLEX.XCF.CDS01

SYS1.PRDPLEX.LOGR.CDS01

SYS1.PRDPLEX.WLM.CDS01

GREENFORD

SYS1.PRDPLEX.LOGR.CDSQ2P

SYS1.PRDPLEX.LOGR.CDSQ1S

SYXQ2P (676B)

SYS1.PRDPLEX.CFRM.CDSQ2S

SYS1.PRDPLEX.XCF.CDSQ2P

SYS1.PRDPLEX.WLM.CDSQ2S

SYS1.PRDPLEX.LOGR.FCDSQ2S

SYXQ1P (4B2E)

SYS1.PRDPLEX.CFRM.CDSQ1P

SYS1.PRDPLEX.XCF.CDSQ1S

SYS1.PRDPLEX.WLM.CDSQ1P

SYS1.PRDPLEX.LOGR.FCDSQ1S

SYXQ2S (676A)

SYS1.PRDPLEX.CFRM.FCDSQ2S

SYS1.PRDPLEX.XCF.FCDSQ2S

SYS1.PRDPLEX.WLM.FCDSQ2S

SYXQ1S (4B2F)

SYS1.PRDPLEX.CFRM.FCDSQ1S

SYS1.PRDPLEX.XCF.FCDSQ1S

SYS1.PRDPLEX.WLM.FCDSQ1S

LOGR01 (4B42)

SYS4.PRDPLEX.LOGREC.ALLRECS

SYXQ1L (4B2D)

SYS1.PRDPLEX.LOGR.CDSQ1S

CF02

IXC_PATH_SMALL

CF01

ISGLOCK

IXC_PATH_LARGE

DPX02S (40C8)

SYS1.DEVPLEX.CFRM.CDS02

SYS1.DEVPLEX.LOGR.CDS01

SYS1.DEVPLEX.WLM.CDS02

SYS1.DEVPLEX.XCF.CDS02

SYS1.DEVPLEX.XCF.CDS04

DPX01P (3425)

SYS1.DEVPLEX.CFRM.CDS01

SYS1.DEVPLEX.LOGR.CDS02

SYS1.DEVPLEX.WLM.CDS01

SYS1.DEVPLEX.XCF.CDS01

SYS1.DEVPLEX.XCF.CDS03

DEVCF02

IXC_PATH_LARGE

DEVCF01

ISGLOCK

IXC_PATH_SMALL

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download