Cisco Systems S/390 manual SAS/C Usage Notes, Obtaining a TCPEEP, Obtaining an SVC Dump

SAS/C Usage Notes

F RUNTCP,TCP SNAP ALL

Obtaining a TCPEEP

Read the Cisco IOS for S/390 System Management for information to help you set up and submit your trace address space and submit the TCPEEP TSO command.

Obtaining an SVC Dump

Read the IBM document MVS/ESA System Commands Reference Summary for the syntax of the required DUMP commands. In particular, include all jobs involved in the problem using the JOBNAME parameter of the DUMP command.

Obtaining JCL Output

Copy the JCL output of RUNTCP to a file using the following procedure:

•If you are using JES2/SDSF, type XDC beside the job listed in SDSF and follow the panel instructions. This will let you copy to a data set of your choice. Generally, for every thousand lines of job output you need three 3390 tracks.

•If you are using JES3, you may use FLASHER or a similar product to copy the RUNTCP output to a data set in a similar fashion.

SAS/C Usage Notes

You must use the SAS 6.0 compiler, header files, object files, and runtime libraries to COMPILE and LINK using the Cisco IOS for S/390 release 2.0 socket library

You can run a down-level (SAS 5.5) c program against Cisco IOS for S/390 release 2.0, and it can be compiled and linked using the Cisco IOS for S/390 release 1.0 (or lower) socket library. However, it must be run using the SAS 5.5 runtime library. This program can then run over the Cisco IOS for S/390 release 2.0 stack.

•Mixing any SAS 6.0 modules/headers with SAS 5.5 modules/headers will cause problems.

•Mixing any Cisco IOS for S/390 release 2.0 socket modules/headers with Cisco IOS for S/390 release 1.0 socket modules/headers will cause problems.

•Mixing runtime modules between releases will cause problems.

In addition, in SAS 6.0, LSCNCOM is always dynamically loaded. If linked with the application program in 6.0, LSCNCOM will cause ABENDs.

Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0

This section provides information on how to convert your Cisco IOS for S/390 release 1.0 configuration files to the configuration files used for Cisco IOS for S/390 release 2.0. There is also a discussion on the use of the LOGGING statement.

Several diagrams are given to show the parameter changes. In the diagrams, parameters not available in Cisco IOS for S/390 release 2.0 are shown crossed out (OLDPARM). New parameters are shown in boldface type (BOLD).

34Cisco IOS for S/390 Release 2.0 Release Notes