Alan:

I have moved the COMMAND statements to the top before the INCLUDE TCPCMSU 
which has DEV  type statements like SPOOL, CONSOLE, LINK and it IPLs CMS. 
Hopefully this is correct now.

USER TCPIP TCPIP 128M 256M ABG 
  COMMAND ATTACH 9400 TO * 9000
  COMMAND ATTACH 9401 TO * 9001 
  COMMAND ATTACH 9402 TO * 9002 
  COMMAND ATTACH 9000 TO * 9000 
  COMMAND ATTACH 9001 TO * 9001 
  COMMAND ATTACH 9002 TO * 9002 
  INCLUDE TCPCMSU 
  OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON 
  SHARE RELATIVE 3000 
  IUCV ALLOW 
  IUCV ANY PRIORITY 
  IUCV *CCS PRIORITY MSGLIMIT 255 
  IUCV *VSWITCH MSGLIMIT 65535 
 * CHANGE SPECIAL FROM 9104 TO 9108 PER SAM  9/30/09 
  SPECIAL 9108 QDIO 3 SYSTEM OSALAN 
  LINK 5VMTCP40 491 491 RR 
  LINK 5VMTCP40 492 492 RR 
  LINK TCPMAINT 591 591 RR 
  LINK TCPMAINT 592 592 RR 
  LINK TCPMAINT 198 198 RR 
  MDISK 191 3390 2258 005 540W02  MR RTCPIP   WTCPIP   MTCPIP 

PROFILE TCPCMSU 
  IPL CMS 
  MACH ESA 
  SPOOL 000C 2540 READER * 
  SPOOL 000D 2540 PUNCH A 
  SPOOL 000E 1403 A 
  CONSOLE 009 3215 T 
  LINK MAINTSYS 0190 0190 RR 
  LINK MAINTSYS 019D 019D RR 
  LINK MAINTSYS 019E 019E RR 
  LINK MAINTSYS 0402 0402 RR 
  LINK MAINTSYS 0401 0401 RR 
  LINK MAINTSYS 0405 0405 RR 

The mprout was indeed a cut and paste error.

But the SYSTEM DTCPARMS is on TCPMAINT's 191 not 198 which is empty.

Also IBM DTCPARMS is named IBMN DTCPARMS on TCPMAINT's 191:

MAINT    FILELIST A0  V 169  Trunc=169 Size=10 Line=1 Col=1 Alt=0  
Cmd   Filename Filetype Fm Format Lrecl    Records     Blocks   Date Time  

      MPROUTE  CONFIG   T1 F         80         47          1 10/09/09 
15:31:10 
      MPROUTES CONFIG   T1 F         80         59          2 10/06/09 
11:28:10 
      MPROUTE  CONFOLD  T1 F         80         58          2  8/19/09 
11:13:31 
      PROFILE  EXEC     T2 V         73         54          1  8/04/09 
12:04:18 
      MPROUTEX CONFIG   T1 F         80         28          1  7/29/09 
12:03:46 
      MPROUTEO CONFIG   T1 F         80        472         10  1/23/09 
16:33:35 
      XXXXX    CONFIG   T1 F         80         20          1  1/23/09 
14:52:04 
      SYSTEM   DTCPARMS T1 F         80        359          8  1/23/09 
14:41:15 
      IBMN     DTCPARMS T1 V         73        359          4  1/15/09 
14:24:33 
      TCPIPO   DATA     T1 V         73        474          5  1/15/09 
12:31:27 
Hope this does not bring Chuckie out.





Alan Altmark <alan_altm...@us.ibm.com> 
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
02/22/2011 06:54 PM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: Changing TCPIP PROFILE EXEC






On Tuesday, 02/22/2011 at 06:00 EST, George Henke/NYLIC 
<george_he...@newyorklife.com> wrote:
> DEV 9000, 9001, 9002 are changing to 9400, 9401, 9402 
> 
> Here is what I have now: 
> 
> TCPIP:  PROFILE EXEC 
> 
> 'Access 198 D' 
> 'Access 591 E' 
> 'Access 592 F' 
> ATT 9000 TCPIP 9000 
> ATT 9001 TCPIP 9001 
> ATT 9002 TCPIP 9002 
> ATT 9100 TCPIP 9100 
> ATT 9101 TCPIP 9101 
> ATT 9102 TCPIP 9102 
> queue "EXEC TCPRUN" 

I will pretend I didn't see that.  I'm not even seeing the lack of quotes 
around the ATTACH commands.  Not looking.... La la la la la la....

> SYSTEM DTCPARMS: 
> 
> :nick.TCPIP     :type.server  :class.stack 
> :nick.DTCVSW1   :type.server  :class.stack 
>                 :owner.MAINT 
 
> 
> :nick.DTCVSW2   :type.server  :class.stack 
>                 :owner.MAINT 
> 
> :nick.ROUTED    :type.server  :class.rip 
> :nick.MPROUTE   :type.server  :class.mprout 

I'll assume a cut/paste error.  That should be "mproute".

> :nick.FTPSERVE  :type.server  :class.ftp 
> :nick.SMTP      :type.server  :class.smtp 

Note that by putting all of those entries in SYSTEM DTCPARMS, you are 
effectively cancelling any entry that IBM put on the matching :type.server 

entry in IBM DTCPARMS.  I would suggest deleting all entries except for 
TCPIP.  At the minimum, delete the DTCVSW1 and DTCVSW2 entries.


> I can change the TCPIP DIRECTORY entry like so: 
> 
> USER TCPIP TCPIP 128M 256M ABG 
>  INCLUDE TCPCMSU 
>  OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON 
>  SHARE RELATIVE 3000 
>  IUCV ALLOW 
>  IUCV ANY PRIORITY 
>  IUCV *CCS PRIORITY MSGLIMIT 255 
>  IUCV *VSWITCH MSGLIMIT 65535 
> * CHANGE SPECIAL FROM 9104 TO 9108 PER SAM  9/30/09 
>  SPECIAL 9108 QDIO 3 SYSTEM OSALAN 
>  LINK 5VMTCP40 491 491 RR 
>  LINK 5VMTCP40 492 492 RR 
>  LINK TCPMAINT 591 591 RR 
>  LINK TCPMAINT 592 592 RR 
>  LINK TCPMAINT 198 198 RR 
>  COMMAND ATTACH 9400 TO * 9000 
>  COMMAND ATTACH 9401 TO * 9001 
>  COMMAND ATTACH 9402 TO * 9002 
>  COMMAND ATTACH 9000 TO * 9000 
>  COMMAND ATTACH 9001 TO * 9001 
>  COMMAND ATTACH 9002 TO * 9002 
>  MDISK 191 3390 2258 005 540W02  MR RTCPIP   WTCPIP   MTCPIP 
> 
> Is this correct? 

Yes, except that COMMAND statement must be placed before any device 
statements.

> Or I can modify DTCPARMS like so: 
> 
> :nick.TCPIP     :type.server  :class.stack :attach.9400-9402 

In this case you must also modify PROFILE TCPIP to change the DEVICE 
statement to point to 9400.  You could instead
    :attach.9400 9000, 9401 9001, 9402 9002

> If so, which would be preferable? 
> 
> I do not see a fallback if I modify DTCPARMS only. 

:attach.9400(OPT) 9000, 9401(OPT) 9001, 9402(OPT) 9002(OPT), 
9000-9002(OPT)

gives the same result.  If you don't put OPT in there, the TCP/IP startup 
program won't throw an error if one of the devices if offline or the 
attach fails.  Again, if you need more sophistication, use the :Exit. tag. 

 Read Chapter 5 of the TCP/IP planning book for details on how to use 
DTCPARMS files.

> But OTOH the DIRECTORY method does not look as permanent. 
> 
> Also why *COMMAND* in the DIRECTORY entry ATTACHes? 
> 
> I thought that is used only in EXECs? 

COMMAND is a valid statement in the directory.  ATTACH is not.  Look in 
the CP Planning book.

> Also can I abbreviate the ATTACH to ATT 9400 * 9000? 

Yes, but don't.  IBM has changed the abbreviations of commands. 
Abbreviations are for humans, not programs.

> Also, the DIRECTORY method has a nice fallback, but what if I corrupt 
the TCPIP 
> DIRECTORY entry when making the change. 
> 
> What is my fallback?  VTAM? 

VTAM?  In general, no, since few systems have VTAM (and it isn't licensed 
on IFLs).  OSA-ICC connections (preferred) or the integrated 3270 console 
are how you access the system in case of TCPIP death.  In extreme cases, 
the linemode integrated console can be used.  If you need to repair TCP/IP 

in this mode, learn to use the ifconfig commands rather than XEDIT.  It's 
easier than using a linemode editor.

Alan Altmark

z/VM and Linux on System z Consultant
IBM System Lab Services and Training 
ibm.com/systems/services/labservices 
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

Reply via email to