Conference smaug::ibm_requests

Currently,  there are two regions with APPC autoinstall support, CICS41B(aka
CIC17B) and CICSLARG.  CICS will use information contained in the partner's
NETNAME and in the VTAM bind to select the most appropriate model on which
to base a new connection.  What does this mean for APPC here?  Any logmode 
with XL62nnnn, XL6Xnnnn, or MODELU62 should work for APPC autoinstall. 

The naming standard you should adhere to should not matter.  Although, you might
wamt to double check you conventions with Windsor.

Please use CICSLARG for independant LU autoinstall support for now.  I will
convert CICSBIG to independant LU autoinstall support in the near future.  I 
will make sure PIPD trnsaction is functional in CICSLARG.

Dave,

  While there is no inherent naming standards that I know 
of, I think a name structure like IINTxxxx will keep an
association with the system name (IBMINT).  These names are 
not in use now.  How big a 'bunch' of LU 6.2 will you be adding?


Thanks,

 Windsor  

Well, my needs are becoming clearer, unfortunately, not crystal clear.

For now I think I can limit my needs to this:

1) A second PU type 2 on ATOG
2) 20 sequential lu definitions on this pu, starting at whatever
   address is customary for a PU Type2.  You can use the first
   atog pu as a model
3) These dependent lu's permanently defined into as many CICS regions as
   makes sense.  Certainly CICSBIG, but I'm unsure of where else these
   should be.
4) As with number 3, I'd like the last 20 of the existing lu's defined
   on PUIBMIN5 (sys1.vtamlst(swibmint)) permanently defined to CICSBIG
   and whatever other CICS's make sense.  That would be IBMIN5EC through
   IBMIN5FF.

Thanks,
Dave.

I have defined a second pu (puatog2) for use with ATOG.	
 Idblk is x'05d', Idnum is x'97012'.  This has 255 Lu's
(dependent) and the same independents that PUATOG has.
The LU names are ATOG201 - ATOG2FE and ATOG2DW2 for the 
dependent lu's (address 01 - 255).
The independent lu's defined in PUATOG2 are ATOG2, ATOG200,
and ATOG2DW1.
	

CEDA Group:		DWAPPC
CEDA list:		BIG4LIST


			DEPENDENT LUs

 Conn  Session  Netname		Conn  Session  Netname
 ----  -------- --------        ----  -------- --------
 I5D1  I5D1SESS IBMIN5EC	A2D1  A2D1SESS ATOG203
 I5D2  I5D2SESS IBMIN5ED        A2D2  A2D2SESS ATOG204
 I5D3  I5D3SESS IBMIN5EE        A2D3  A2D3SESS ATOG205
 I5D4  I5D4SESS IBMIN5EF        A2D4  A2D4SESS ATOG206
 I5D5  I5D5SESS IBMIN5F0        A2D5  A2D5SESS ATOG207
 I5D6  I5D6SESS IBMIN5F1        A2D6  A2D6SESS ATOG208
 I5D7  I5D7SESS IBMIN5F2        A2D7  A2D7SESS ATOG209
 I5D8  I5D8SESS IBMIN5F3        A2D8  A2D8SESS ATOG20A
 I5D9  I5D9SESS IBMIN5F4        A2D9  A2D9SESS ATOG20B
 I5D0  I5D0SESS IBMIN5F5        A2DA  A2DASESS ATOG20C
 I5DA  I5DASESS IBMIN5F6        A2DB  A2DBSESS ATOG20D
 I5DB  I5DBSESS IBMIN5F7        A2DC  A2DCSESS ATOG20E
 I5DC  I5DCSESS IBMIN5F8        A2DD  A2DDSESS ATOG20F
 I5DD  I5DDSESS IBMIN5F9        A2DF  A2DFSESS ATOG210
 I5DE  I5DESESS IBMIN5FA        A2DG  A2DGSESS ATOG211
 I5DF  I5DFSESS IBMIN5FB        A2DH  A2DHSESS ATOG212
 I5DG  I5DGSESS IBMIN5FC        A2DI  A2DISESS ATOG213
 I5DH  I5DHSESS IBMIN5FD        A2DJ  A2DJSESS ATOG214
 I5DI  I5DISESS IBMIN5FE        A2DK  A2DKSESS ATOG215
 I5DJ  I5DJSESS IBMIN5FF        A2DL  A2DLSESS ATOG216  


			INDEPENDENT LUs

				A2I1  A2I1SESS ATOG2
				A2I2  A2I2SESS ATOG2DW1
				A2I3  ATOG200  ATOG200	

Hi,

Does the second PU for ATOG, PUATOG2, still exists ..?

I couldn't activate this PU from my MS SNA Server, and also through netview I 
couldn't see the definition of this PU either.

regards
-Jay

Hi Jay,

   The definition does still exist, I had not set it up as 
auto activate.  I have varied it active for you and put it 
into the same switched major node as puatog.

Windsor