Communications Server for Data Center Deployment

There are several examples provided in the Enterprise Extender Implementation Guide (Redbook SG247359.pdf). You can get this from the Comm. Server Educational Material Website:

Education Materials for Communications Server for Data Center Deployment

  Chapter 4 has VTAM configuration examples, then Chapters 6 and 7 have AIX, Linux (respectively) with VTAM Switch Major Node examples.

Jeff L Smith

Comm. Server Development

Jeff,

Thanks for the references.  I will review and let you know if I have any further questions.

Regards,

Wayne Murray

Jeff,

I reviewed the documentation you referenced for defining the CS on Linux SNA node to VTAM via EE and it seems to agree with how we have it defined.

We are able to activate the node on VTAM and it connects and its VTAM PU comes active.  Status from the Linux side of the node also indicates that it is connected and active.

On the Linux side there is an LU defined for a CICS emulation region that is not running yet.  This LU defined under the active SNA node on the Linux side shows as active on Linux.  Yet when we display their PU on the mainframe this LU does not show up as I expected.  Is there something we have to do on VTAM to define this LU under their PU?  I expected it to be dynamic.  I suspect there is something not setup properly on the Linux side. 

Thanks,

Wayne Murray

If the PU is active on VTAM and the Comm. Server, then there is a DLUS/DLUS connection between the CS Linux and VTAM that will manage the PU/LU activity.

The 2 systems only use the "pu_id" (CS Linux) and "IDBLK/NUM" (VTAM) to match up the same PU each side has configured. The LUs are reference between each system using only the LU number (CS Linux) or LOCADDR (VTAM). If these match up, then they both will be reference the same LUs. (Section 7.3.3. of the Enterprise Extender Guide) 
Could the LU number be different between the 2 systems, like 1 on Linux and 2 on VTAM? 

The /var/opt/ibm/sna/sna.err (Error log file) on Linux will show any errors in activition. If you have Auditing activated, the sna.aud file in the same directory will show the PU and LU being activated for SSCP and for LU-LU sessions. To activate auditing on Linux, the command is "snaadmin set_log_type,audit=YES". 

The "snaadmin status_dependent_lu" will show the PU name and LU name on Linux where you can match up numbers against the LOCADDR configured on VTAM.

Jeff L Smith

Comm. Server Development. 

Additionally, If the LUs being used for CICS are LU6.2 (independent LUs), then VTAM would not need to define any LUs on the Comm. Server. The only VTAM configuration needed is a PU definition, which is the CP Name of the Comm. Server on Linux. CICS can use both dependent and independent LUs. The Enterprise Extender Guide sections 7.3.3 and 7.3.4 cover these for using EE.

Jeff L Smith

Jeff,

In this case this LU under the CS LInux PU will be an LU 6.2 independent LU.  I have verified that our VTAM has start option DYNLU=YES.  So, as I understand it, I do not have to define this LU under the PU on VTAM.  It should be defined dynamically when the CS for LInux PU connects to VTAM, correct?  And should it then show up under the Linux PU when we display it on VTAM?

Thanks,

Wayne Murray   

It may show up under the VTAM PU defined for the Linux if the CICS LU is on the same VTAM.

It may not show up if CICS is on another SNA node. In this case, the EE RTP connection may pass through the Network Node VTAM using ANR. It would show up on the CICS node dynamically.

LUs that are defined on the CS Linux will only show up on VTAM if the sessions the are ending on the local VTAM. Any LU the uses the Network Node VTAM to have its session routed to another VTAM will not show up on that Network Node. It will show up on the end point of the session. 

You may be looking for the LU, but the LU is not ending it session on the VTAM, just passing through on it link into the network. If the CICS LU is local, then it will show up. You should see it active with the Mode table it is using. 

Jeff L Smith