links: コピーブランド スーパーコピー 財布 スーパーコピーブランド ブランド コピー 時計 スーパーコピー ブランドコピー激安

Mainframe LPAR Add or Remove

CONTENTS:

Bottom

1. Configuration

2. IOCDS resources  added/removed  (channels, devices, consoles) for the  new LPAR BC4A

3. IODF definitions  added/removed   for the  new LPAR BC4A

4. System  definitions & changes in z/OS

5. HMC definitions, changes and IPL for  LPAR BC4A

6. Profile definitions & changes in PC/Console server

7. TCPIP profile definitions & changes of LPAR BC4A in z/OS

8. Balance of MIPS and MSU

9. TSO users access to the new LPAR BC4A

 

The present paper describes the thechnology for adding or removing  an LPAR to existing Mainframe configuration with its base configuration components – CPU, disks storage, tapes storage, consoles,  ESCON channels, TCP/IP and Ethernet  connections. IOCDS resources  are added/removed  for the  new LPAR  and IODF definitions  for them are corrected in the similar way. To prepare IPL for  the new LPAR   all the necessary system data sets and system volumes have to be prepared and new IPL and IODF parameters volumes added. HMC definitions, changes and operations are necessary to be performed before new IPL. Profile definitions & changes should be performed in the consoles server for the emulated new consoles of this LPAR.  TCPIP profile definitions & changes  are necessary to be done in the z/OS system facilities of the LPAR to permit access to it from any TSO users on local or remote terminals. To be all the LPAR’s  balanced against MIPS and MSU of the Mainframe some actions in HMC should be performed .

 

          1. Configuration

The existing  Mainframe configuration of IBM consists of the following components:  CPU, disk volumes devices, tape volume devices, consoles for  each LPAR on PC/Consoles server in OS2/WARP,  ESCON channels, LAN Ethernet  connections, OSA-Express TCP/IP network connections, HMC (Hardware Management Console  with Primary support element in OS2/WARPfor all Mainframe hardware configuration operations as follows:

 

– CPU/MF: – connected  to PC/HMC(Primary support element – OS2/WARP)  via ESCON channel

                         – connected via OSA-Express TCP/IP network connections to  Ethernet  (permitting  TSO remote/local users to have PC/3270 communication  to IP of different  LPAR’s)

                           – connected via ESCON channel to PC/Consoles server that is connected also  to the existing  LAN via   Ethernet connection.

                           – connected to disk volumes drives via ESCON channels having CTC/CNC device access

                          – connected to disk volumes drives via ESCON channels having CTC/CNC device access

          2. IOCDS resources  added/removed  (channels, devices, consoles) for the  new LPAR BC4A

To add another image LPAR BC4A  to existing CPC  it is necessary to add (include) in IOCDS the resources of the new LPAR:  name & partition  number   (if BC4A,4) in RESOURCE PARTITION definition,  Control units (CUNUMBRs and paths of disks, tapes, consoles  for this partition number  in  CNTLUNIT definitions), Device addresses (of disks, tapes, consoles  for this partition number with the  respective CUNUMBRs in IODEVICE definitions) as follows:

RESOURCE PARTITION=((BC1B,1),(BC2A,2),(BC3A,3),(BC4A,4)) – added new LPAR BC4A

 

CHPID PATH=02,TYPE=OSD,SHARED –   channel path for OSA-Express card in  TCP/IP OSA-Express network standard  connection (QDIO)  for all LPARs

CHPID PATH=04,TYPE=OSE,SHARED –   channel path for OSA-Express card in  TCP/IP OSA-Express network minimized  function connection (non- QDIO) for all LPARs

CHPID PATH=0D,TYPE=CNC,SHARED –   channel path for ESCON  CNC LPAR consoles

CHPID PATH=1F,TYPE=CTC,SHARED –   channel path for ESCON CTC   channel adapter

CHPID PATH=16,TYPE=CNC,SHARED –   channel path for ESCON  CNC channel adapter

CHPID PATH=20,TYPE=CNC,SHARED –   channel path for ESCON  CNC channel adapter

CHPID PATH=25,TYPE=FC,SHARED –   channel path for   FICON (fibre connection channel)

CHPID PATH=27,TYPE=FC,SHARED –   channel path for   FICON (fibre connection channel)

CNTLUNIT CUNUMBR=0002,PATH=(02),UNIT=OSA – OSA QDIO control unit address for all LPARs

CNTLUNIT CUNUMBR=0110,PATH=(20),UNIT=SCTC,UNITADD=((00,16)),CUADD=1 –  CTC control unit address  for the old existing  LPARs.

CNTLUNIT CUNUMBR=0120,PATH=(20),UNIT=SCTC,UNITADD=((00,16)),CUADD=2 –  CTC control unit address  for the old existing  LPARs.

CNTLUNIT CUNUMBR=0130,PATH=(20),UNIT=SCTC,UNITADD=((00,16)),CUADD=3 –  CTC control unit address  for the old existing  LPARs.

CNTLUNIT CUNUMBR=0140,PATH=(20),UNIT=SCTC,UNITADD=((00,16)),CUADD=4added CTC control unit address  for the new LPAR BC4A.

CNTLUNIT CUNUMBR=0400,PATH=(04),UNIT=OSA –  OSA non- QDIO control unit address for all LPARs

CNTLUNIT CUNUMBR=0E90,PATH=(16,0E),UNIT=3590,UNITADD=((00,2)) – ESCON cartridge 3590 tapes control unit address for all LPARs

CNTLUNIT CUNUMBR=0D03,PATH=(0D),UNIT=3174,UNITADD=((00,16)),CUADD=3  added console  control unit  address of   IBM 3174  for the new LPAR BC4A.

CNTLUNIT CUNUMBR=3A00,PATH=(25,27),UNIT=2105,UNITADD=((00,256)),      X    –

CUADD=04 – added control unit  address  for new disk volumes IBM 2105 if needed for LPAR BC4A.

IODEVICE ADDRESS=(0110,16),UNITADD=00,CUNUMBR=(0110),UNIT=SCTC,       X

PARTITION=(BC2A,BC3A,BC4A) – added CTC device access from  the new LPAR BC4A to other LPARs.

IODEVICE ADDRESS=(0120,16),UNITADD=00,CUNUMBR=(0120),UNIT=SCTC,       X

PARTITION=(BC1B,BC3A,BC4A) added CTC device access from  the new LPAR BC4A to other LPARs.

IODEVICE ADDRESS=(0130,16),UNITADD=00,CUNUMBR=(0130),UNIT=SCTC,       X

PARTITION=(BC1B,BC2A,BC4A) added CTC device access from  the new LPAR BC4A to other LPARs.

IODEVICE ADDRESS=(0140,16),UNITADD=00,CUNUMBR=(0140),UNIT=SCTC,       X

PARTITION=(BC1B,BC2A,BC3A) )  added CTC device access  to  the new LPAR BC4A  from the other LPARs.

IODEVICE ADDRESS=(0300,2),CUNUMBR=(0E90),UNIT=3590 – existing IBM 3590 tape  device addresses   for all LPARS

 

IODEVICE ADDRESS=(0960,15),UNITADD=00,CUNUMBR=(0400),UNIT=OSA – existing  non-QDIO  TCP/IP OSA device addresses   for all LPARS

IODEVICE ADDRESS=(096F),UNITADD=FE,CUNUMBR=(0400),UNIT=OSAD – existing  non-QDIO TCP/IP OSA device addresses   for all LPARS

IODEVICE ADDRESS=(0990,15),UNITADD=00,CUNUMBR=(0002),UNIT=OSA – existing  QDIO TCP/IP OSA device addresses   for all LPARS

IODEVICE ADDRESS=(099F),UNITADD=FE,CUNUMBR=(0002),UNIT=OSAD – existing QDIO TCP/IP OSA device address   for all LPARS

 

IODEVICE ADDRESS=(0A00,16),CUNUMBR=(0D03),UNIT=3278,MODEL=2,          X

PARTITION=(BC4A) – added console device address  for the new LPAR BC4A.

IODEVICE ADDRESS=(500,256),CUNUMBR=(3A00),UNIT=3390,STADET=Y –  added disk  device addresses  if new volumes needed for the new LPAR BC4A.

 

CUNUMBR value (given by hardware engineer for the real I/O configuration) is defined in IOCDS with  command CNTLUNIT.

IODEVICE ADDRESS value (given by hardware engineer for the real I/O configuration) is defined in IOCDS with  command IODEVICE.

After building the new  IOCDS (look the article   ZOS  IOCDS  data set  creation  using Hardware Management Console     and loading (activating) it  with POR function, you will find  in HMC operations (Primary support element – Groups – CPC/Images – Images) the added new  IMAGE of the desired new LPAR   (if  BC4A,4). In this    LPAR you can install any Operating system (suppose ZOS)  with all necessary system programs and definitions according the new IOCDS and the new IODF created for this LPAR (look the article ZOS  test  IODF configuration  display/ create/ change-consoles/ compare  using ISPF   ).

If the above definitions are removed from IOCDS, after  activating it again with POR function, the added  IMAGE of the new LPAR   (if  BC4A,4) will disappear. If by any chance (not removed some parameter) the BC4A image still appears  in –  Primary support element – Groups – CPC/Images – Images –  and if you want to load it (in  CPC Recovery – Load function), an Exception   will occur that “Conditions Not Met, requiring BC4A to be activated”. If you try to activate BC4A via Daily – ACTIVATE function – the  message ‘BC4A Not operational link’  will access appear .

 

          3. IODF definitions  added/removed   for the  new LPAR BC4A

If using TSO/ISPF and after selecting Option HC – 6th (Maintain I/O definition files) – 2 (Copy I/O definition file) – the existing IODF (I/O definition file)  SYS1.IODF38.WORK is copied to new  IODF (I/O definition file) SYS1.IODF48.WORK. (Look the article ZOS  test  IODF configuration  display/ create/ change-consoles/ compare  using ISPF  ). After Copy operation you  may add/change I/O definition for chosen Control Unit (CUNUMBR) or  Device  as described for Device (Look the article ZOS  test  IODF configuration  display/ create/ change-consoles/ compare  using ISPF  )   in ‘2.2. Change I/O Device  Definition’:  HC – 1 – 5 -/ (Actions on selected devices) -2 (Change Device Definition)  etc. …  and  for CUNUMBR:  HC – 1 – 4 -/ (Actions on selected control units) -2 (Change Control Unit Definition)   etc… If the new  ‘SYS1.IODF48. WORK’  is prepared as shown in  Case 2,  the next step is to build the  Production I/O Definition File  SYS1.IODF48  as described  in the same article.

If  the  JCL source library is used (Look the article  ZOS  test  IODF configuration  display/ create/ change-consoles/ add- disks  using JCL source library  ) the following statements define the requested configuration in the  source library member of IODF42 with the new LPAR BC4A included  according  the new IOCDS in p.2 above:

 

* CONFIGURATION for z/OS140                     *

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

TITLE ‘MVSCP FOR z/OS140 – CONFIGURATION 42

PRINT NOGEN

CONFIG42 IOCONFIG ID=42

ID    MSG1=’IODF For Production  – BC2A’,SYSTEM=(2066,1)

RESOURCE PARTITION=((BC1B,1),(BC2A,2),(BC3A,3),(BC4A,4)) – added new LPAR BC4A

 

****     #2365 – OSA EXPRESS GIGABIT ETHERNET SLOT 5

CHPID PATH=(02),TYPE=OSD,SHARED –  channel path for standard  connection (QDIO)

****     #2366 – OSA EXPRESS FAST ETHERNET SLOT 6 non- QDIO

CHPID PATH=(04),TYPE=OSE,SHARED – channel path for min. funct.  connection (non-QDIO)

****     #2323 – 16-PORT ESCON CARD SLOT 11

CHPID PATH=(0D),TYPE=CNC,SHARED,                              X

PARTITION=((BC1B,BC2A,BC3A,BC4A)) –  channel path for ESCON  CNC all consoles

****     #2323 – 16-PORT ESCON CARD SLOT 12

CHPID PATH=(16),TYPE=CNC,SHARED –  channel path for ESCON CTC  channel adapter

CHPID PATH=(1F),TYPE=CTC,SHARED,                              X

PARTITION=((BC1B,BC2A,BC3A,BC4A)) –  channel path for ESCON CTC  channel adapter

CHPID PATH=(20),TYPE=CNC,SHARED,                              X

PARTITION=((BC1B,BC2A,BC3A,BC4A)) –  channel path for ESCON CTC  channel adapter

****     #2320 – 2-PORT FICON CARD SLOT 9

CHPID PATH=(25),TYPE=FC,SHARED,                               X

PARTITION=((BC1B,BC2A,BC3A)) – channel path for   FICON (fibre connection channel)

****     #2320 – 2-PORT FICON CARD SLOT 10

CHPID PATH=(27),TYPE=FC,SHARED,                               X

PARTITION=((BC1B,BC2A,BC3A)) – channel path for   FICON (fibre connection channel)

*** NEW CNC

*** CNTLUNIT AND IODEVICES FOR BC1B

CNTLUNIT CUNUMBR=0110,PATH=(20),UNITADD=((00,16)),            X

UNIT=SCTC,CUADD=1 –  CTC control unit address  for the old existing  LPAR BC1B.

IODEVICE ADDRESS=(0110,16),CUNUMBR=(0110),UNITADD=00,         X

UNIT=SCTC,PART=(BC2A,BC3A,BC4A) – added CTC device access from  the new LPAR BC4A to other LPARs.

*** CNTLUNIT AND IODEVICES FOR BC2A

CNTLUNIT CUNUMBR=0120,PATH=(20),UNITADD=((00,16)),            X

UNIT=SCTC,CUADD=2 –  CTC control unit address  for the old existing  LPAR BC2A.

IODEVICE ADDRESS=(0120,16),CUNUMBR=(0120),UNITADD=00,         X

UNIT=SCTC,PART=(BC1B,BC3A,BC4A) – added CTC device access from  the new LPAR BC4A to other LPARs.

*** CNTLUNIT AND IODEVICES FOR BC3A

CNTLUNIT CUNUMBR=0130,PATH=(20),UNITADD=((00,16)),            X

UNIT=SCTC,CUADD=3 –    CTC control unit address  for the old existing  LPAR BC3A.

IODEVICE ADDRESS=(0130,16),CUNUMBR=(0130),UNITADD=00,         X

UNIT=SCTC,PART=(BC1B,BC2A,BC4A) – added CTC device access from  the new LPAR BC4A to other LPARs.

*** CNTLUNIT AND IODEVICES FOR BC4A

CNTLUNIT CUNUMBR=0140,PATH=(20),UNITADD=((00,16)),            X

UNIT=SCTC,CUADD=4  added CTC control unit address  for the new LPAR BC4A.

IODEVICE ADDRESS=(0140,16),CUNUMBR=(0140),UNITADD=00,         X

UNIT=SCTC,PART=(BC1B,BC2A,BC3A)  added CTC device access  to  the new LPAR BC4A  from the other LPARs.

*** FOR BC4A; CUADD=3 FOR 2074

CNTLUNIT CUNUMBR=0D03,PATH=0D,UNITADD=((00,16)),CUADD=3,      X

UNIT=3174 added console  control unit  address of  IBM 3174  for the new LPAR BC4A.

IODEVICE ADDRESS=(A00,16),CUNUMBR=(0D03),UNITADD=00,          X

UNIT=3278,PART=BC4A – added console device address  for the new LPAR BC4A.

*** QDIO OSA

CNTLUNIT CUNUMBR=0002,PATH=02,UNIT=OSA – OSA QDIO control unit address for all LPARs

IODEVICE ADDRESS=(990,15),CUNUMBR=(0002),UNIT=OSA,UNITADD=00 – existing  QDIO TCP/IP OSA device addresses   for all LPARS

IODEVICE ADDRESS=(99F),CUNUMBR=(0002),UNIT=OSAD,UNITADD=FE – existing  QDIO TCP/IP OSA device addresse   for all LPARS

*** NON-QDIO OSA

CNTLUNIT CUNUMBR=0400,PATH=04,UNIT=OSA –  OSA non- QDIO control unit address for all LPARs

IODEVICE ADDRESS=(960,15),CUNUMBR=(0400),UNIT=OSA,UNITADD=00 – existing  non-QDIO  TCP/IP OSA device addresses   for all LPARS

IODEVICE ADDRESS=(96F),CUNUMBR=(0400),UNIT=OSAD,UNITADD=FE – existing  non-QDIO  TCP/IP OSA device addresses   for all LPARS

**** —- ESCON CARTRIDGE 3590E –

CNTLUNIT CUNUMBR=0E90,PATH=16,UNIT=3590,                      X

UNITADD=((00,2)) – ESCON cartridge 3590 tapes control unit address for all LPARs

IODEVICE ADDRESS=(0300,2),CUNUMBR=(0E90),STADET=Y,            X

UNIT=3590,UNITADD=00,OFFLINE=YES,FEATURE=(COMPACT) – existing IBM 3590 tape  device addresses   for all LPARS

**** —- ESS (SHARK) – 2105/800

CNTLUNIT CUNUMBR=3A00,PATH=(25,27),                           X

UNITADD=((00,256)),UNIT=2105,CUADD=4 – added control unit  address  for new disk volumes IBM 2105 if needed for LPAR BC4A.

IODEVICE UNIT=3390,ADDRESS=(0500,256),CUNUMBR=(3A00),         X

UNITADD=00,STADET=Y,OFFLINE=YES –  added disk  device addresses  if new volumes needed for the new LPAR BC4A.

The  source statement definitions  of IODF above are   included in JCL job  for assembly, LE and creating   the new IODF DATA SET  (as SYS1.IODEF42 file)  on  IODF DEVICE (volume BC2MCC with address 1904). This is shown in the article  ZOS  test  IODF configuration  display/ create/ change-consoles/ add- disks  using JCL source library  .

After building the new  IODF (using ISPF as described in article ZOS  test  IODF configuration  display/ create/ change-consoles/ compare  using ISPF   or   using JCL  as described in article ZOS  test  IODF configuration  display/ create/ change-consoles/ add- disks  using JCL source library  )   the IPL should be performed   with the suffix of  this new IODF.

To remove LPAR BC4A from existing IODF  it is necessary to remove   the above definitions in IODF (using  ISPF or JCL changes  according the respective articles) and  after building the  new  IODF (the restored  old one  before adding BC4A parameters) you will find that the IPL with this IODF will be not possible for LPAR BC4A (if   BC4A image is existing still).

 

          4. System  definitions & changes in z/OS

To prepare IPL for  the new LPAR BC4A all the necessary system data sets and system volumes have to be prepared. New IPL and IODF parameters volumes for  LPAR  BC4A should be created (or restored from full disk backup tapes of the new BC4A system). The   BC2MCC (parameters volume) with address 1900 and BC2RIC (IPL volume) with address 1904 are the BC4A IPL system volumes as follows:

 IODF DEVICE 1904   VOLUME BC2MCC

IPL DEVICE 1900 VOLUME BC2RIC

 

The next  steps should be performed before IPL:

 

The library member LOAD42  in library SYS1.IPLPARM (volume BC2MCC with address 1904) is  created to point the new IODF SYS1.IODEF42 as follows:

IODF     42 SYS1     BC1B     42

NUCLEUS  1

NUCLST   00 Y

SYSCAT   BC2MCC113CCATALOG.MVSICFM.VBC2MCC

SYSPLEX  BC2APLEX

PARMLIB  SYS1.PARMLIB

PARMLIB  CPAC.PARMLIB

IEASYM   00

The pointed  library SYS1.PARMLIB (in volume BC2MCC with address 1904)  of  member LOAD42 contains also some  important members as follows:

COMMND00 – member with set of commands to  vary online/offline physical addresses of disk volumes during IPL process for this new  LPAR BC4A,  commands to start VTAM network,  start RMF,  ..  etc.

IEASYS00 – member setting some   system BC4A parameters.

SMFPRM00 – member setting   SMF parameters

 

          5. HMC definitions, changes and IPL for  LPAR BC4A

To   start   IPL  load menu for  LPAR BC4A  from  HMC in CPU/Mainframe (look at article ZOS  Hardware Management Console  I/O  configuration operations  )  do  the following:

– Position and mark CPC,  choose  and mark  BACKZ800, position and mark – Single object operations using  right mouse button    to enter  Primary Support Element.

–  From IBM Primary Support Element – choose  GROUPS – position and mark CPC – from TASK LIST – choose CPC Configuration menu – then I/O Configuration function   and position the desired configuration A0 (if this is the  last IOCDS with the new LPAR BC4A).

– From Task list – choose CPC recovery – mark POR (Power off  reset) – enter – all active LPAR’s appear in red – confirm YES to POR – Choose I/O configuration (IOCDS) A0 /with the  new BC4A  LPAR / – confirm to POR for restart –  Wait 7 minutes to stop.

– If necessary to  activate/deactivate LPAR BC4A – from   GROUPS – choose   IMAGES – mark BC4A – from  TASK LIST – chose   Daily – press  Activate/Deactivate.

–  To activate all LPARs   – press GROUPS – choose  –  IMAGES  – mark all LPARs – using right mouse button and  TASK  LIST  – chose   Daily find  ACTIVATE – press enter to activate all partitions – wait to finish.

– To  load (IPL)  I/O configuration for  LPAR BC4A – from   GROUPS – choose   IMAGES – mark BC4A –   from TASK LIST – choose  CPC Recovery – press  Load  –  enter the following data for LPAR BC4A:

Load address: 1900 – IPL device 

Load Parameter: 190442 – IPL parm   (if the new IODF SYS1.IODEF42 for LPAR BC4A is chosen)

and press
2 times Enter.

 

          6. Profile definitions & changes in PC/Console server

From PC console server start  PC 3270 session bc4aa00 (with IP address = 127.0.0.1, LU= BC4AA00, port=3270)   for  the  emulated LPAR BC4A  console /with PC console server internal setting to LU= BC4AA00 for   the new IOCDS definition: IODEVICE ADDRESS= (0A00,16), CUNUMBR=(0D03), UNIT=3278, MODEL=2,  PARTITION=(BC4A)/ (look the article Mainframe CONSOLES restore  ). To be more clear, you have to be   aware that the PC consoles  server (where the transformations  of  z/OS console addresses to IP addresses  are made) is connected directly with   ESCON channel to CPU/Mainframe from one side and at  the same time  to   Ethernet  connection of the existing LAN.

After IPL – go to  LPAR BC4A  console on session bc4aa00 and answer if some replies are necessary to finish IPL
of  LPAR BC4A.

 

          7. TCPIP profile definitions & changes of LPAR BC4A in z/OS

The TCPIP procedure of LPAR BC4A that is started during of   BC4A IPL is defined in the procedure  library  BC4A.ZOS140.STCPROC  where the member TCPPROF from  library BC4A.ZOS140.PARMLIB is  pointed. To assign IP to the new image (LPAR BC4A), enter  the  requested   member TCPPROF (TCPIP profile definitions) from library  BC4A.ZOS140.PARMLIB and  detect the place:

HOME

10.212.4.98       BC2AJES

where to   put  the desired  IP address (if 10.212.4.98) of this LPAR.   To have access from  any IP of TSO users from the existing  LAN  to this LPAR, it is necessary to add in TCPPROF  the respective routes (BEGINROUTES:  Route 10.150.20.0/24 10.212.4.3 BC2AJES MTU 1500   etc…).

To verify or activate TCPPROF after updates enter the following commands from TSO/ISPF – sd.log:

– /d tcpip,,t,conn – display tcpip current connections

EZZ6064I TELNET CONNECTION DISPLAY 398

EN                                           TSP

CONN     TY IPADDR..PORT            LUNAME   APPLID   PTR LOGMODE

——– — ———————- ——– ——–  — ——–

000944DB    10.150.20.112..61268   TCP00091 BC2AT001  TAE SNX32702

0009446A    10.150.20.28..63293    TCP00089 BC2AC50A  TAE SNX32702

00094468    10.150.20.28..63291    TCP00088 BC2AC20A  TAE SNX32702

00094465    10.150.20.28..63288    TCP00087 BC2AC30A  TAE SNX32702

00094463    10.150.20.28..63287    TCP00086 BC2AC10A  TAE SNX32702

0007AAB0    10.212.4.99..53667     TCP00197           TPE

—– PORT:      23    ACTIVE           PROF: CURR CONNS:      6

————————————————————

8 OF 8 RECORDS DISPLAYED

AS READY FOR COMMANDS.

– /v tcpip,,0,bc4a.zos140.parmlib(tcpprof) – activate tcp after update in
bc4a.zos140.parmlib(tcpprof)

 

          8. Balance of MIPS and MSU

While creating the new LPAR BC4A  if you wish to  determine what to be done  so that all the LPARS are balanced – do the following:

In Primary support element of HMC  go to – Groups – CPC/Images – Images – select     IMAGE (BC4A,4)  of the new LPAR  BC4A   – then select from Task list – CPC Operational Customization – choose Customize/Delete Activation  Profiles – and for Not Dedicated central processors  – enter Processor – Initial Processor weight – 10 (1 – 999) – the same as for the others partitions if 10 is assigned  for them. For Storage – Initial – enter 1024 MB (or any up to 8192  if this is maximum).

The balance of MIPS and MSU among the LPAR’s is very complex task and heavy to be
achieved precisely.

 

          9. TSO users access to the new LPAR BC4A

To have access from   any TSO user from the existing  LAN or from emulated PC/3270 remote  screens start   PC/3270 (or Nexus Terminal) emulation session of TSO PC  terminal, go to Communication – Configure  –  Attachment: Telnet3270 –   Link Parameters  – and  set   Host Name or IP address : 10.212.4.98 (if  this is  set in  member TCPPROF of library bc4a.zos140.parmlib as

HOME

10.212.4.98       BC2AJES).

The same access to the new LPAR BC4A may be achieved from  PC/Console server     PC 3270 emulation session,  when go to Communication – Configure –   Link Parameters  – and set   Host Name or IP address: 10.212.4.98  (if  LPAR BC4A /IP= 10.212.4.98).

For both cases you can obtain access from any TSO user to any LPAR of CPU/Mainframe when setting   the respective LPAR Host Name or
IP address.

End of document

Incoming search terms:

  • lpar in mainframe
  • what is lpar in mainframe
Choose donation amount:

Leave A Reply

Comments

No comments yet, be the first to add one!

Places

 

Choose donation amount:
您要找的资源已被删除、已更名或暂时不可用。 Clef two-factor authentication