> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-ims/tcp-ims-documentacion-tecnica/anexos.md). # Anexos ## Lista de módulos ### Ejecutables
ZTBPBCDAZTBPBCSOZTBPBSTOZTBPEBDAZTBPELIS
ZTBPETCP
### Fuentes de DLI
ZTBPBCDAZTBPBCSOZTBPDDADZTBPDDAIZTBPDSOD
ZTBPDSOIZTBPEBDAZTBPELISZTBPETCPZTBPFDAD
ZTBPFDAIZTBPFSODZTBPFSOI
### JCLs
ZTBPFLISZTBPFLI1ZTBPJBDAZTBPJCDAZTBPJCSO
ZTBPJLISZTBPJLI1ZTBPJTCPZTBPJTC1
## Definiciones TCP/IP ### Procedimiento de arranque de TCP ```cobol 000001 //TCPIPB2 PROC PARMS='CTRACE(CTIEZB00)' 000003 //* Communication Server/390 000004 //* SMP/E Distribution Name: EZAEB01G 000006 //* 5647-A01 (C) Copr. IBM Corp. 1991,1997. 000007 //* All rights reserved. 000008 //* US Government Users Restricted Rights - 000009 //* Use, duplication or disclosure restricted 000010 //* by GSA ADP Schedule Contract with IBM Corp. 000011 //* See IBM Copyright Instructions 000014 //TCPIP EXEC PGM=EZBTCPIP, 000015 // PARM='&PARMS', 000016 // REGION=32M,TIME=1440 000018 //* The C runtime libraries should be in the system's link list 000019 //* or add them via a STEPLIB definition here. If you add 000020 //* them via a STEPLIB, they must be APF authorized with DISP=SHR 000022 //STEPLIB DD DSN=TCPIP.SEZALINK,DISP=SHR 000023 // DD DSN=TCPIP.SEZALNK2,DISP=SHR 000025 //* SYSPRINT contains run-time diagnostics from TCPIP. It may be 000026 //* a data set or SYSOUT. 000027 //* ALGPRINT contains run-time diagnostics from TCPIP's Autolog 000028 //* task. It should be SYSOUT. 000029 //* SYSERROR contains error messages from TCPIP that occurred 000030 //* while processing the PROFILE. 000031 //* 000032 //SYSPRINT DD SYSOUT=*,DCB=(RECFM=FB,LRECL=137,BLKSIZE=137) 000033 //ALGPRINT DD SYSOUT=*,DCB=(RECFM=FB,LRECL=137,BLKSIZE=137) 000034 //SYSOUT DD SYSOUT=*,DCB=(RECFM=FB,LRECL=137,BLKSIZE=137) 000035 //CEEDUMP DD SYSOUT=*,DCB=(RECFM=FB,LRECL=137,BLKSIZE=137) 000036 //SYSERROR DD SYSOUT=* 000037 //* 000038 //* TNDBCSCN is the configuration data set for TELNET DBCS 000039 //* transform mode. 000040 //* 000041 //*TNDBCSCN DD DSN=TCPIP.SEZAINST(TNDBCSCN),DISP=SHR 000043 //* TNDBCSXL contains binary DBCS translation table codefiles 000044 //* used by TELNET DBCS Transform mode. 000045 //* 000046 //*TNDBCSXL DD DSN=TCPIP.SEZAXLD2,DISP=SHR 000048 //* TNDBCSER receives debug output from TELNET DBCS Transform 000049 //* mode, when TRACE TELNET is specified in the PROFILE data set. 000050 //* 000051 //*TNDBCSER DD SYSOUT=* 000053 //* TCPIP reads the parameters from a data set with name 000054 //* TCPIP.nodename.TCPIP or with name TCPIP.PROFILE.TCPIP. 000055 //* See the chapter on "Configuring the TCPIP Address Space" in 000056 //* the Configuration Guide for more information. A sample of 000057 //* such a profile is included in member SAMOPROF of the 000058 //* SEZAINST data set. 000059 //* 000060 //PROFILE DD DISP=SHR,DSN=TCPIP.SEZAINST(CPUBPRO2) 000062 //* SYSTCPD explicitly identifies which data set is to be 000063 //* used to obtain the parameters defined by TCPIP.DATA. 000064 //* The SYSTCPD DD statement should be placed in the TSO logon 000065 //* procedure or in the JCL of any client or server executed 000066 //* as a background task. The data set can be any sequential 000067 //* data set or a member of a partitioned data set (PDS). 000068 //* 000069 //* For more information please see "Understanding TCP/IP Data 000070 //* Set Names" in the Configuration Guide. 000071 //* 000072 //SYSTCPD DD DSN=TCPIP.SEZAINST(TCPDATB2),DISP=SHR ****** **************************** Bottom of Data **************************** ``` ### Fichero TCPIP.PROFILE ``` TCPIP.PROFILE.TCPIP ; =================== ; ; COPYRIGHT = NONE. ; ; This is a sample configuration file ; for the TCPIP address space. ; ; NOTES: ; ; The device configuration statements MUST be changed to match your ; hardware and software configuration. ; ; The BEGINVTAM section must be changed to match your VTAM ; configuration. ; ; ; For more information about this file, see "Configuring the TCPIP ; Address Space" and "Configuring the Telnet Server" in the ; Configuration Guide. ; ; ; ---------------------------------------------------------------------- ; ; ; Flush the ARP tables every 20 minutes. ; ARPAGE 20 ; ; You can specify DATASETPREFIX in the PROFILE.TCPIP but it no longer ; has any affect on the TCP/IP stack. ; ; ---------------------------------------------------------------------- ; ; Set Telnet time-out to 10 minutes. ; TELNETPARMS PORT 23 INACTIVE 600 TIMEMARK 600 SCANINTERVAL 120 SMFINIT STD SMFTERM STD WLMCLUSTERNAME TN3270E ENDWLMCLUSTERNAME ENDTELNETPARMS ; ---------------------------------------------------------------------- ; ; AUTOLOG the following servers. ; AUTOLOG 5 ; FTPD JOBNAME FTPD1 ; FTP Server ; FTPDB ; FTP Server de la CPU-B ; LPSERVE ; LPD Server ; NAMESRV ; Domain Name Server ; NCPROUT ; NCPROUTE Server ; PORTMAP ; Portmap Server ; OROUTED ; RouteD Server ; RXSERVE ; Remote Execution Server ; SMTP ; SMTP Server ; OSNMPD ; SNMP Agent Server ; SNMPQE ; SNMP Client ; TCPIPX25 ; X25 Server ENDAUTOLOG ; ; ---------------------------------------------------------------------- ; ; Reserve ports for the following servers. ; ; NOTES: ; ; A port that is not reserved in this list can be used by any user. ; If you have TCP/IP hosts in your network that reserve ports ; in the range 1-1023 for privileged applications, you should ; reserve them here to prevent users from using them. ; ; The port values below are from RFC 1060, "Assigned Numbers." ; PORT 7 UDP MISCSERV ; Miscellaneous Server 7 TCP MISCSERV 9 UDP MISCSERV 9 TCP MISCSERV 19 UDP MISCSERV 19 TCP MISCSERV 20 TCP OMVS NOAUTOLOG ; FTP Server 21 TCP FTPD1 ; FTP Server 23 TCP OMVS ; TELNET SERVER 25 TCP SMTP ; SMTP Server 53 TCP NAMESRV ; Domain Name Server 53 UDP NAMESRV ; Domain Name Server 111 TCP PORTMAP ; Portmap Server 111 UDP PORTMAP ; Portmap Server 135 UDP LLBD ; NCS Location Broker 161 UDP OSNMPD ; SNMP Agent 162 UDP SNMPQE ; SNMP Query Engine 512 TCP RXSERVE ; Remote Execution Server 514 TCP RXSERVE ; Remote Execution Server 515 TCP LPSERVE ; LPD Server 520 UDP OROUTED ; RouteD Server 580 UDP NCPROUT ; NCPROUTE Server 750 TCP MVSKERB ; Kerberos 750 UDP MVSKERB ; Kerberos 751 TCP ADM@SRV ; Kerberos Admin Server 751 UDP ADM@SRV ; Kerberos Admin Server 3000 TCP CICSTCP ; CICS Socket 7777 TCP KI1056EI ; IMS Socket ; ; ---------------------------------------------------------------------- ; ; Hardware definitions: ; ; NOTE: To use these device and link statements, update the statements ; to reflect your installation configuration and remove the semicolon ; ; ; LOSAB4 osa2 with a Token-Ring and Ethernet adapter. ; DEVICE LOSAB4 LCS 1004 LINK OSAB4TCP IBMTR 0 LOSAB4 ;LINK ETH1 ETHERNET 1 LCS1 ; ; LCS2 is a 3172 Model 2 with a FDDI adapter. ; ;DEVICE LCS2 LCS BE0 ;LINK FDDI1 FDDI 0 LCS2 ; ; SNALU0 is an SNA Link. ; ;DEVICE SNALU0 SNAIUCV SNALINK LU000000 SNALINK ;LINK SNA1 IUCV 1 SNALU0 ; ; ---------------------------------------------------------------------- ; ; HOME Internet (IP) addresses of each link in the host. ; ; NOTE: To use this home statement, update the ipaddress and linknames ; to reflect your installation configuration and remove the semicolon ; HOME 192.168.172.089 OSAB4TCP ; ; --------------------------------------------------------------------- ; ; The PRIMARYINTERFACE statement is used to specify which interface ; is the primary interface. ; ; If PRIMARYINTERFACE is not specified, then the first link in the HOME ; statement is the primary interface, as usual. ; ; NOTE: To use this primary statement, update the and linkname ; to reflect your installation configuration and remove the semicolon ; PRIMARYINTERFACE OSAB4TCP ; ; ---------------------------------------------------------------------- ; ; IP routing information for the host. All static IP routes should ; be added here. ; ; NOTE: To use this GATEWAY statement, update the addresses and links ; to reflect your installation configuration and remove the semicolon ; GATEWAY ; ; Direct Routes - Routes that are directly connected to my interfaces. ; ; Network First Hop Link Name Packet Size Subnet Mask Subnet Value 192.168.172 = OSAB4TCP 1500 0 ; ; Indirect Routes - Routes that are reachable through routers on my ; network. ; ; Network First Hop Link Name Packet Size Subnet Mask Subnet Value ; 193.12.2 130.50.10.1 TR1 2000 0 ; 10.5.6.4 193.5.2.10 ETH1 1500 HOST ; ; Default Route - All packets to an unknown destination are routed ; through this route. ; ; Network First Hop Link Name Packet Size Subnet Mask Subnet Value DEFAULTNET 192.168.172.254 OSAB4TCP DEFAULTSIZE 0 ; ; ---------------------------------------------------------------------- ; ; orouted Routing Information ; ; if you are using orouted, comment out the GATEWAY statement and ; update the BSDROUTINGPARMS statement to reflect your installation ; configuration and remove the semicolon ; ; Link Maxmtu Metric Subnet Mask Dest Addr ; BSDROUTINGPARMS false ; TR1 2000 0 255.255.255.0 0 ; ETH1 1500 0 255.255.255.0 0 ; FDDI1 DEFAULTSIZE 0 255.255.255.0 0 ; ENDBSDROUTINGPARMS ; ; ---------------------------------------------------------------------- ; ; Use TRANSLATE to specify the hardware address of a specific IP ; address. See the Customization and Administration Guide for more ; information. ; TRANSLATE ; A null translate statement issues the warning message EZZ0323I ; ; ---------------------------------------------------------------------- ; ; Turn off all tracing. If tracing is to be used, change the following ; line. To trace the configuration component, for example, change ; the line to ITRACE ON CONFIG 1 ; ITRACE OFF ; ; ---------------------------------------------------------------------- ; The ASSORTEDPARMS NOFWD will prevent the forwarding of IP packets ; between different networks. If NOFWD is not specified, IP packets ; will be forwarded between networks when this host is a gateway. ; ASSORTEDPARMS NOFWD ENDASSORTEDPARMS ; NOFWD issues the informational message EZZ0334I ; ; ---------------------------------------------------------------------- ; ; Define the VTAM parameters required for the Telnet server. ; BEGINVTAM ; Define logon mode tables to be the defaults shipped with the ; latest level of VTAM TELNETDEVICE 3278-2-E NSX32702 ; 24 line screen - default of NSX32702 TELNETDEVICE 3279-2-E NSX32702 ; 24 line screen - default of NSX32702 TELNETDEVICE 3278-3-E NSX32703 ; 32 line screen - default of NSX32702 TELNETDEVICE 3279-3-E NSX32703 ; 32 line screen - default of NSX32702 TELNETDEVICE 3278-4-E NSX32704 ; 48 line screen - default of NSX32702 TELNETDEVICE 3279-4-E NSX32704 ; 48 line screen - default of NSX32702 TELNETDEVICE 3278-5-E NSX32705 ; 132 column screen - default of NSX327 TELNETDEVICE 3279-5-E NSX32705 ; 132 column screen - default of NSX327 ; ; Define las direcciones IP de Técnica de Sistemas ; IPGROUP DirSiste 192.168.168.67 192.168.168.68 192.168.168.72 ENDIPGROUP ; LUGROUP LuSiste ip2sis01..ip2sis03 ENDLUGROUP ; LUMAP LuSiste DirSiste ; LUSESSIONPEND ; On termination of a Telnet server connection, ; the user will revert to the DEFAULTAPPL USSTCP USSBSC DirSiste ALLOWAPPL * ; Allow all applications that have not been LINEMODEAPPL NOLASE ENDVTAM ; ; ---------------------------------------------------------------------- ; ; Start all the defined devices. ; ; NOTE: To use these START statements, update the device name ; to reflect your installation configuration and remove the semicolon ; START LOSAB4 ; START LCS2 ; START SNALU0 ``` ### Fichero TCPIP.DATA ``` ;*********************************************************************** ; * ; Name of Data Set: TCPIP.DATA * ; * ; COPYRIGHT = NONE. * ; * ; This data, TCPIP.DATA, is used to specify configuration * ; information required by TCP/IP client programs. * ; * ; * ; Syntax Rules for the TCPIP.DATA configuration data set: * ; * ; (a) All characters to the right of and including a ; will be * ; treated as a comment. * ; * ; (b) Blanks and are used to delimit tokens. * ; * ; (c) The format for each configuration statement is: * ; * ; keyword value * ; * ; where is an optional label that can be * ; specified before a keyword; if present, then the keyword- * ; value pair will only be recognized if the SystemName matches * ; the node name of the system, as defined in the IEFSSNxx * ; PARMLIB member. This optional label permits configuration * ; information for multiple systems to be specified in a single * ; TCPIP.DATA data set. * ; * ; NOTE: You should define the SystemName in the IEFSSNxx * ; PARMLIB member to be the same as your JES2 or JES3 * ; node name. This is required for correct delivery of * ; SMTP mail. * ; * ;*********************************************************************** ; TCPIPJOBNAME specifies the name of the started procedure that was ; used to start the TCPIP address space. TCPIP is the default. ; TCPIPJOBNAME TCPIPB2 ; ; HOSTNAME specifies the TCP host name of this system. If not ; specified, the default HOSTNAME will be the node name specified ; in the IEFSSNxx PARMLIB member. ; ; For example, if this TCPIP.DATA data set is shared between 2 ; systems, OURMVSNAME and YOURMVSNAME, then the following 2 lines ; will define the HOSTNAME correctly on each system. ; ;OURMVSNAME: HOSTNAME OURTCPNAME ;YOURMVSNAME: HOSTNAME YOURTCPNAME ; HOSTNAME OS390B2 ; ; DOMAINORIGIN specifies the domain origin that will be appended ; to host names passed to the resolver. If a host name contains ; any dots, then the DOMAINORIGIN will not be appended to the ; host name. ; ;DOMAINORIGIN YOUR.DOMAIN.NAME DOMAINORIGIN TEL.INDRA.ES ; ; NSINTERADDR specifies the IP address of the name server. ; LOOPBACK (127.0.0.1) specifies your local name server. If a name ; server will not be used, then do not code an NSINTERADDR statement. ; (Comment out the NSINTERADDR line below). This will cause all names ; to be resolved via site table lookup. ; ;NSINTERADDR 127.0.0.1 NSINTERADDR 172.29.2.41 NSINTERADDR 192.168.1.30 ; ; NSPORTADDR specifies the foreign port of the name server. ; 53 is the default value. ; NSPORTADDR 53 ; ; RESOLVEVIA specifies how the resolver is to communicate with the ; name server. TCP indicates use of TCP virtual circuits. UDP ; indicates use of UDP datagrams. The default is UDP. ; RESOLVEVIA TCP ; ; RESOLVERTIMEOUT specifies the time in seconds that the resolver ; will wait to complete an open to the name server (either UDP or TCP). ; The default is 30 seconds. ; RESOLVERTIMEOUT 30 ; ; RESOLVERUDPRETRIES specifies the number of times the resolver ; should try to connect to the name server when using UDP datagrams. ; The default is 1. ; RESOLVERUDPRETRIES 1 ; ; TRACE RESOLVER will cause a complete trace of all queries to and ; responses from the name server or site tables to be written to ; the user's console. This command is for debugging purposes only. ; ; TRACE RESOLVER ; ; ; You can specify DATASETPREFIX in the PROFILE.TCPIP and TCPIP.DATA ; data sets. The character string specified as a parameter on ; DATASETPREFIX takes precedence over both the distributed or modified ; data set prefix name as changed by the EZAPPRFX installation job. ; If this statement is used in a profile or configuration ; data set that is allocated to a client or a server, then ; that client or server dynamically allocates additional required data ; sets using the value specified for DATASETPREFIX as the data set name ; prefix. The DATASETPREFIX parameter can be up to 26 characters long ; and the parameter must NOT end with a period. ; ; For more information please see "Understanding TCP/IP Data Set ; Names" in the Customization and Administration Guide. ; DATASETPREFIX TCPIP ; ; ; MESSAGECASE MIXED indicates to the FTP server, FTP client, TELNET ; client, and PING client that all messages should be displayed in ; mixed case. MESSAGECASE UPPER indicates to the FTP server, FTP ; client, TELNET client, and PING client that all messages should ; be displayed in uppercase. Mixed case inserts in messages will ; will not be uppercased. ; If MESSAGECASE is not specified, mixed case messages will be used. ; ; MESSAGECASE MIXED ; MESSAGECASE UPPER ; ; LOADDBCSTABLES indicates to the FTP server and FTP client which DBCS ; translation tables should be loaded at initialization time. Remove ; from the list any tables that are not required. If LOADDBCSTABLES is ; not specified, no DBCS tables will be loaded. ; ; LOADDBCSTABLES JIS78KJ JIS83KJ SJISKANJI EUCKANJI HANGEUL KSC5601 ; LOADDBCSTABLES TCHINESE BIG5 SCHINESE ;*********************************************************************** ; ; End of file. ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-ims/tcp-ims-documentacion-tecnica/anexos.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.