CA-L-Serv Configuration Tasks › Verify the Communications Server Installation

Verify the Communications Server Installation

If you do not plan to use CA‑L‑Serv on multiple systems or if you will not use the CA‑L‑Serv Communications Server, you may skip this section.

The Installation Verification Procedure for the Communications Server ensures that CA‑L‑Serv tasks running on different systems are able to establish communication and exchange messages.

The following procedure may be repeated between every pair of systems that will use CA‑L‑Serv to establish communication.

To verify the Communications Server installation

1. Tailor the JCL members HJ35IVC1 and HJ35IVC2.

   Customize the following templates available in members HJ35IVC1 and HJ35IVC2, which the installation placed in the CCCSJCL data set.

   Receiving job:

   //HJ35IVC1 JOB (JOBACCNT)                   (1)
   //MAMS0001 EXEC PGM=LDMAMS
   //STEPLIB  DD   DISP=SHR,DSN=CAI.CCCSLOAD     (2)
   //SSN$xxxx DD   DUMMY                       (3)
   //SYSPRINT DD   SYSOUT=X
   //SYSIN    DD   *
     COMMTEST                                  (4)
     RECEIVE
     END
   /*
   

   Sending job:

   //HJ35IVC2 JOB (JOBACCNT)                   (1)
   //MAMS0001 EXEC PGM=LDMAMS
   //STEPLIB  DD   DISP=SHR,DSN=CAI.CCCSLOAD     (2)
   //SSN$xxxx DD   DUMMY                       (3)
   //SYSPRINT DD   SYSOUT=X
   //SYSIN    DD   *
     COMMTEST                                  (4)
     WAIT APPL(HJ35IVC1)
     SEND
     END
   /*
   

   Footnotes:

   (1) Provide a valid job card.

   (2) Change to the CA‑L‑Serv target library.

   (3) Replace xxxx by the z/OS subsystem name that you specified in your CA‑L‑Serv start procedure.

   (4) The SYSIN statements in both jobs are self‑explanatory.

   Important! The two jobs must have different job names.

2. Start CA‑L‑Serv on both systems.

   Start CA‑L‑Serv on the two z/OS systems that will run the test.

   Important! You must ATTACH both the Communications Server and the File Server to run this test successfully.

3. Submit HJ35IVC1.

   Submit this job on the first of the two systems. This job will emulate a client application that will receive a message from his partner on the second z/OS system. HJ35IVC1 will wait until it receives data from the sending system.

4. Submit HJ35IVC2.

   Submit this job on the second of the two z/OS systems. The job sends 512 bytes of data to job HJ35IVC1 running on the other system. Both jobs should end immediately after this job is submitted.

5. Verify the results.
   • Browse the spooled output of job HJ35IVC1. You should see the following messages:

           COMMTEST
     LDM0829I CommServer initialization returned  RC=0000  Reason=0000
           RECEIVE
     LDM0832I Receive complete: APPL=HJ35IVC2 QUAL=COMMTEST Length=512
           END
     LDM0829I CommServer LCOMSHUT returned  RC=0000  Reason=0000
     

   • Browse the spooled output of job HJ35IVC2. You should see the following:

           COMMTEST
     LDM0829I CommServer initialization returned  RC=0000  Reason=0000
           WAIT APPL(HJ35IVC1)
           SEND
     LDM0829I CommServer send returned  RC=0000  Reason=0000
           END
     LDM0829I CommServer LCOMSHUT returned  RC=0000  Reason=0000
     

   Any return code higher than 0 from both jobs indicates a problem.

   The Communications Server installation is verified.