Anthony,

Okay.  Just wanted to make sure before I gave you things that would not help 
you.

It is not that bad and you just need to make sure of the following.

1)  Make sure you do have a separate values in your DEVSUPxx for each LPAR.  I 
use the first two positions as my LPAR and leave the last two to match the 
defaults.  Example, MEDIA1=1001, MEDIA2=1002,.....MEDIA10=100A,ERROR=100E and 
PRIVATE=100F for LPAR1 and then use 20xx for LPAR2.

2)  You need to make sure you have USERMOD CL05244 installed.  Make sure you 
update CTSUXENT with your library name(s).

3)  In your CTSUXENT module, add some code like the code below.  Pay attention 
that columns 72-80 are important to insert into the correct location of your 
current source.  My code is set up to perform this check at the very beginning 
so that we don't do anything if the tape is not correct.  I have the sequence 
numbers set to update the mode and added in after the Load Address (LA) of 
ATLTABLE into R9 and before the ATLFIND DSECT.  In the case below, it could 
have been done with one check; however, it was set up to allow for multiple 
prefixes, if needed.

./ CHANGE NAME=CTSUXENT
* ********************************************************************  01790100
*     @MYCO - ADDED THE VOLUME SECTIONS TO ONLY PROCESS THE REQUIRED *  01790110
*             TAPES DEPENDING ON THE LPAR AND LEAVE THE REMAINING    *  01790120
*             TAPES FOR THE OTHER OAM SYSTEMS TO PROCESS.  MVSX LPAR *  01790130
* ********************************************************************  01790140
CHKVOL   DS    0H                                                       01790150
         CLC   WKVOLSER(2),=C'XN'      IS THIS A MVSX NATIVE ATL2?      01790200
         BE    ACCTAPE                    NO LEAVE FOR OTHER OAM        01790210
         CLC   WKVOLSER(1),=C'X'       IS THIS A MVSX VIRTUAL VTS2?     01790220
         BNE   RC16                       NO LEAVE FOR OTHER OAM        01790230
ACCTAPE  DS    0H                                                       01790240
* @MYCO - END OF MYCO CUSTOM CODE                                       01790250
* ********************************************************************  01790260

4)  Make sure your CA-1 version of CBRUXENT, CBRUXEJC and CBRUXVNL are applied 
to the z/OS system to override the IBM RMM default delivered in LINKLIB.

5)  Make sure CA-1 is up and running BEFORE OAM is started.  IF not, the exits 
will not be there to REJECT the tapes.


I hope this helps.  Please feel free to contact me off-line if needed.




Thanks,

Craig

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Anthony Fletcher
Sent: Monday, March 10, 2014 22:51
To: [email protected]
Subject: Re: CBRUXENT using CA-1 in VTS 7700 environment

Craig

Yes, that is exactly the environment.


regards,
Anthony Fletcher - NZ MIITP
Team Lead NZ SMM
(AirNZ, Westpac NZ ,  NWM AU)

IBM Strategic Outsourcing Delivery
Server Systems Operations
Server Management Mainframe

Mainframe Software Program Manager  NZ
z/OS Technical Lead A/NZ

Ph: Direct +64 4 576 8142, tieline 61 929 8142,             ITN *869298142,
mobile +64 21 464 864, Fax +64 4 576 5808.
Internet: [email protected]<mailto:[email protected]>, Sametime: 
[email protected]<mailto:[email protected]>

 "The biggest threat to effective communication is the belief that it has 
occurred"
 "Winners make commitments, Losers make promises"



From:   Craig Pace <[email protected]<mailto:[email protected]>>
To:     [email protected]<mailto:[email protected]>,
Date:   11/03/2014 16:42
Subject:        Re: CBRUXENT using CA-1 in VTS 7700 environment
Sent by:        IBM Mainframe Discussion List 
<[email protected]<mailto:[email protected]>>



Anthony,

Wanting to make sure what you are asking.  Do you mean that you have two LPARs 
which share the same VTS hardware; however, don't share the TMC?  If your 
answer is yes, then are you also asking about making sure that LPAR1 does not 
insert tapes from LPAR2 and vice versa?

If there are correct, then let me know.  Using DEVSUP and minor exit changes to 
the CA-1 exits can take care of this without any issues.
Currently running that way today with a TS7740 and I have 5 separate TMCs using 
the save hardware, different volumes, different DEVSUP and minor USERMOD 
changes to prevent he LPAR from picking up the wrong tapes.




Thanks,

Craig
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Thomas Conley
Sent: Monday, March 10, 2014 22:34
To: [email protected]<mailto:[email protected]>
Subject: Re: CBRUXENT using CA-1 in VTS 7700 environment

On 3/10/2014 10:32 PM, Anthony Fletcher wrote:
> Question for a CA-1 guru.
> I have a CBRUXENT exit that defines the VTS, which I believe is
necessary, but it also checks that the right CARTs care coming through.
There are two operating modes which have different DEVSUP settings and 
different CA-1 TMC setups.
> I suspect that checking the VOLSERS that appear is redundant.
> Does anyone familiar with is complicated CA-1/OAM/SMS set up have any
useful insight?

Anthony,

All CBRUXENT does for CA-1 is convert the 8-character library name to ROBTYP 
and ROBID.  It's pretty straightforward.  DEVSUPxx should make no difference.

Regards,
Tom Conley

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected]<mailto:[email protected]> with the message: 
INFO IBM-MAIN ________________________________

This communication contains information which is confidential and may also be 
privileged. It is for the exclusive use of the intended recipient(s). If you 
are not the intended recipient(s), please note that any distribution, copying 
or use of this communication or the information in it is strictly prohibited. 
If you have received this communication in error, please notify the sender 
immediately and then destroy any copies of it.

________________________________

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected]<mailto:[email protected]> with the message: 
INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected]<mailto:[email protected]> with the message: 
INFO IBM-MAIN


  ________________________________

This communication contains information which is confidential and may also be 
privileged. It is for the exclusive use of the intended recipient(s). If you 
are not the intended recipient(s), please note that any distribution, copying 
or use of this communication or the information in it is strictly prohibited. 
If you have received this communication in error, please notify the sender 
immediately and then destroy any copies of it.
  ________________________________

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to