MAKESITE command

Use MAKESITE as a TSO command or in a batch job to generate new hlq.HOSTS.SITEINFO and hlq.HOSTS.ADDRINFO data sets. The parameters are the same for either a TSO command or a batch job invocation of MAKESITE.

Tip: Use ETC.IPNODES (in the format etc/ipnodes) to define local hosts tables as the preferred alternative to MAKESITE. For more information, see Resolver configuration in the z/OS Communications Server: IPv6 Network and Application Design Guide, which discusses the use of IPNODES by the resolver to locate IPv4 and IPv6 addresses and site names.

Format

Read syntax diagramSkip visual syntax diagram
>>-MAKESITE--+-----------+--,----------------------------------->
             '-HLQ=--hlq-'      

>--+-----------------------------+--,--------------------------->
   '-MGMTclas=--management_class-'      

>--+-----------------------+--,--+--------------------------+--->
   '-DATAclas=--data_class-'     '-STORclas=--storage_class-'   

>--,--+-------------+--,--+------------------------+-----------><
      '-Unit=--unit-'     '-VOLser=--volume_serial-'   

Parameters

HLQ=hlq
The high-level qualifier of both the input and output data sets. The name specified is appended to the HOSTS.LOCAL, HOSTS.SITEINFO and HOSTS.ADDRINFO data set names.

Minimum abbreviation: HLQ=,
Maximum length: 29 characters

MGMTclas=management_class
The SMS-managed management class. MGMTCLAS is valid only in an SMS environment.

Minimum abbreviation: MGMT=
Maximum length: eight characters

DATAclas=data_class
The SMS-managed data class. DATACLAS is valid only in an SMS environment.

Minimum abbreviation: DATA=
Maximum length: eight characters

STORclas=storage_class
The SMS-managed storage class. STORCLAS is valid only in an SMS environment.

Minimum abbreviation: STOR=
Maximum length: eight characters

Unit=unit
An esoteric device name.

Minimum abbreviation: U=
Maximum length: eight characters

VOLser=volume_serial
Volume serial number.

Minimum abbreviation: VOL=
Maximum length: 6 characters

Usage

Examples

If your current active HLQ was TCPIP.MVSA, you would follow these steps to run MAKESITE and rename the output data sets.
  1. Run MAKESITE with the appropriate parameters to generate 2 new data sets from the new hlq.HOSTS.LOCAL data set.
    As a TSO command, you might enter:
    MAKESITE HLQ=TCPIP.H0004,MGMT=M0001,VOLSER=STRG01,UNIT=SYSDA
    As a batch job, you might use this JCL:
    //MAKESITE JOB ,TIME=2,NOTIFY=USER7
    //*
    //BATCH  EXEC PGM=MAKESITE,REGION=8000K,
    //  PARM='VOLSER=STRG01,UNIT=SYSDA,HLQ=TCPIP.H0004,MGMT=M0001'
    //*
    //STEPLIB DD DISP=SHR,DSN=TCPIP.SEZALOAD
    //SYSPRINT  DD  SYSOUT=*,DCB=(LRECL=132,RECFM=FBA,BLKSIZE=3960)
    //SYSABEND  DD  SYSOUT=*
    //
    Note the following information:
    • This JCL is not shipped with TCP/IP.
    • The size of the parameter string is limited to 100 bytes.
    • Keywords in the parameter string can be abbreviated as shown in the MAKESITE syntax descriptions.
    • Region size varies according to your configuration. Make sure that the region size specified is valid for your configuration.

    This will create TCPIP.H004.HOSTS.SITEINFO and TCPIP.H0004.HOSTS.ADDRINFO.

  2. Rename your existing HOSTS.SITEINFO and HOSTS.ADDRINFO data sets. These data sets are currently accessed by TCP/IP users on the system and should not be deleted while TCP/IP is running.

    For example, change TCPIP.MVSA.HOSTS.SITEINFO to TCPIP.MVSA.HOSTS.SITEOLD and TCPIP.MVSA.HOSTS.ADDRINFO to TCPIP.MVSA.HOSTS.ADDROLD.

  3. Rename the new HOSTS.ADDRINFO and HOSTS.SITEINFO data sets to replace the old ones.

    For example, change TCPIP.H0004.HOSTS.SITEINFO to TCPIP.MVSA.HOSTS.SITEINFO and TCPIP.H0004.HOSTS.ADDRINFO to TCPIP.MVSA.HOSTS.ADDRINFO.

The following example shows the output when the MAKESITE command is run as a batch job. When the MAKESITE command is run as a TSO command, the report format is the same except that the message numbers are not displayed.
Tip: Messages with numbers that end with an "E" (for errors) or a "W" (for warning) are issued when an error occurs. Messages with numbers that end with an "I" are informational messages and do not represent a problem. Some of the messages in the following example reflect internal processing statistics.
EZA0549I                     S T A T I S T I C S            
EZA0550I DATASET: USER40.HOSTS.LOCAL                        
EZA0551I      TOTAL LINES: 24                               
EZA0552W      BAD LINES: (SKIPPED) 0                        
EZA0553I      DUPLICATE NAMES: 0                            
EZA0554I      CONFLICTS IN FIRST 8 LETTERS: 0               
EZA0555I      1 NETWORKS, 1 GATEWAYS, 4 HOSTS               
EZA0556I DATASET: USER40.HOSTS.SITEINFO          
EZA0557I      TABLE SIZE: 13                     
EZA0558I      TOTAL ENTRIES: 4                   
EZA0559I      DISTINCT NAMES: 5                  
EZA0560I      COLLISIONS: 1                      
EZA0561I      AVERAGE PROBES/NAME: 1.200         
EZA0562I DATASET: USER40.HOSTS.ADDRINFO          
EZA0563I      TABLE SIZE: 11                     
EZA0564I      TOTAL ENTRIES: 5                   
EZA0565I      COLLISIONS: 0                      
EZA0566I      NAMES DROPPED: 0                   
EZA0549I
Identifies the start of the MAKESITE statistics report.
EZA0550I
Displays the name of the HOSTS.LOCAL data set processed by the MAKESITE command. The indented lines following this message apply to the HOSTS.LOCAL data set.
EZA0551I
Displays the total number of lines in the HOSTS.LOCAL data set, including comment lines.
EZA0552W
Displays the number of lines in the HOSTS.LOCAL data set that were not processed because of syntax errors.
EZA0553I
Displays the number of duplicate names found in the HOSTS.LOCAL data set.
EZA0554I
Displays the number of potential conflicts. A potential conflict is detected if an address defined in the HOSTS.LOCAL data set maps to multiple names and the first 8 bytes of these names are the same.
EZA0555I
Displays the number of each record type in the HOSTS.LOCAL data set. Valid record types are NET, GATEWAY, and HOST. The number displayed for hosts includes the entry generated by the MAKESITE command for the loopback address.
EZA0556I
Displays the name of the HOSTS.SITEINFO data set. The indented lines following this message apply to the HOSTS.SITEINFO data set.
EZA0557I
Displays the number of table entries created in the HOSTS.SITEINFO data set.
EZA0558I
Displays the number of HOSTS.SITESINFO table entries used and shown as Total Entries in this report.
EZA0559I
Displays the number of names processed (excluding duplicates) and shown as Distinct Names in this report. There can be more Distinct Names than Total Entries if an address maps to more than one name.
EZA0560I
Displays the number of times a hash value was mapped to a slot that was already in use; this value is shown as Collisions in this report. This message is informational only and does not indicate a problem.
EZA0561I
Displays the result of the following calculation: 1 + (Collisions /Distinct Names).
EZA0562I
Displays the name of the HOSTS.ADDRINFO data set. The indented lines following this message apply to the HOSTS.ADDRINFO data set.
EZA0563I
Displays the number of table entries created in the HOSTS.ADDRINFO data set.
EZA0564I
Displays the number of HOSTS.SITESINFO table entries used.
EZA0565I
Displays the number of times a hash value was mapped to a slot that was already in use. This message is informational only and does not indicate a problem.
EZA0566I
Displays the number of names that were dropped because more than six names were mapped to a particular address.

Usage

After running the MAKESITE command, you can test the correctness of the hlq.HOSTS.ADDRINFO and hlq.HOSTS.SITEINFO data sets with the TESTSITE command.