gtpm5m18Messages (Online)

DMAP-DNSS

DMAP0001ILINK MAP DATA DISPLAY ccccvv ACTIVE IN LOADSET lsnameb C LOAD MODULE ADDRESS - address C LOAD MODULE SIZE - size

Where:

ccccvv
The name and version of the C load module.

lsnameb
The name of the loadset or BASE.

address
Main storage address of the C load module (in hexadecimal).

size
Size of the C load module (in hexadecimal).

Explanation: This is the normal response for the ZDMAP command. This message is followed by a display of the link map data for the specified C load module.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDMAP command.

DMAP1000ELOADSET lsname IS NOT VALID. IT MUST BE GREATER THAN 4 CHARACTERS IF THE LOADSET NAME IS NOT BASE.

Where:

lsname
The name of the loadset.

Explanation: The loadset name must be from 5 to 8 characters with the exception of a loadset name of BASE.

System Action: No link map data is displayed.

User Response: Enter the ZDMAP command again with the LOADSET parameter specifying a valid loadset name that is 5 to 8 characters long.

See TPF Operations for more information about the ZDMAP command.

DMAP1001EINPUT MESSAGE FORMAT INCORRECT. ENTER ZDMAP HELP TO SEE THE CORRECT FORMAT.

Explanation: The format of the ZDMAP command is not correct.

System Action: The ZDMAP command is rejected.

User Response:

  1. Determine the correct format of the ZDMAP command.
  2. Enter the ZDMAP command again using the correct format.

See TPF Operations for more information about the ZDMAP command.

DMAP2000EPROGRAM prognamevv IS NOT A C LOAD MODULE

Where:

prognamevv
The name and version of the program.

Explanation: One of the following errors occurred:

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP command.

DMAP2001EFIND ERROR ON eee RECORD. CANNOT PROCESS ZDMAP REQUEST.

Where:

eee
The E-type loader (ELDR) record, which can be the ELDR master record (EMR), ELDR program directory (EPD) record, or ELDR loadset directory (LSD) record.

Explanation: An input/output (I/O) error occurred while trying to access one of the E-type loader (ELDR) file records for processing the ZDMAP command.

System Action: No link map data is displayed.

User Response: Review any previous error messages for information about the type of error that occurred.

See TPF Operations for more information about the ZDMAP command.

DMAP2002ELOADSET PARAMETER VALID ONLY AFTER E-TYPE LOADER RESTART HAS COMPLETED

Explanation: The ZDMAP command was entered with the LOADSET parameter specified before E-type loader restart ended.

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP command.

DMAP2003ELOADSET PARAMETER VALID ONLY WHEN E-TYPE LOADER RECORDS HAVE BEEN ALLOCATED

Explanation: No E-type loader records (#OLDx) are defined for the TPF system. Therefore, you cannot specify the LOADSET parameter when you enter the ZDMAP command.

System Action: No link map data is displayed.

User Response: Enter the ZDMAP command again and do not specify the LOADSET parameter.

See TPF Operations for more information about the ZDMAP command.

DMAP2004EPROGRAM progname NOT FOUND

Where:

progname
The name of the program.

Explanation: One of the following errors occurred:

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP, ZOLDR ACTIVATE, and ZOLDR DISPLAY commands.

DMAP2005EPROGRAM progname IS UNALLOCATED. CANNOT PROCESS BASE VERSION

Where:

progname
The name of the program.

Explanation: The ZDMAP command was entered with the LOADSET parameter value of BASE specified for a program that is not allocated. Unallocated programs do not have a base version.

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP and ZDPAT commands.

DMAP2006ELOADSET lsname DOES NOT EXIST

Where:

lsname
The name of the loadset.

Explanation: The ZDMAP command was entered with the LOADSET parameter specified for a specific loadset name that could not be found.

System Action: No link map data is displayed.

User Response: Do the following:

  1. Enter ZOLDR DISPLAY ALL to display information about all the loadsets.
  2. Enter the ZDMAP command again with the LOADSET parameter specifying a valid loadset name.

See TPF Operations for more information about the ZDMAP and ZOLDR DISPLAY commands.

DMAP2007ELOADSET lsname IS BEING LOADED. CANNOT PROCESS ZDMAP REQUEST.

Where:

lsname
The name of the loadset.

Explanation: The ZDMAP command was entered with the LOADSET parameter specified for a specific loadset name that is currently being loaded. You cannot display link map data for any programs contained in that loadset.

System Action: No link map data is displayed.

User Response: Enter the ZDMAP command again after the loadset is loaded.

See TPF Operations for more information about the ZDMAP command.

DMAP2008ELOADSET lsname IS BEING ACCEPTED. ENTER ZDMAP AGAIN WITH THE LOADSET PARAMETER SPECIFYING A VALUE OF BASE

Where:

lsname
The name of the loadset.

Explanation: The ZDMAP command was entered with the LOADSET parameter specified for a specific loadset name that is currently being accepted because of a previous ZOLDR ACCEPT command. You cannot display link map data for any programs contained in that loadset. The TPF system considers programs in that loadset to be part of the base version.

System Action: No link map data is displayed.

User Response: Enter the ZDMAP command again and specify the LOADSET parameter with a value of BASE.

See TPF Operations for more information about the ZDMAP and ZOLDR ACCEPT commands.

DMAP2009ELOADSET lsname IS BEING DELETED. CANNOT PROCESS ZDMAP REQUEST.

Where:

lsname
The name of the loadset.

Explanation: The ZDMAP command was entered with the LOADSET parameter specified for a specific loadset name that is marked for deletion and can no longer be accessed. You cannot display link map data for any programs contained in that loadset.

System Action: No link map data is displayed.

User Response: None.

See TPF Operations for more information about the ZDMAP command.

DMAP2010EPROGRAM progname DOES NOT EXIST IN LOADSET lsname

Where:

progname
The name of the program.

lsname
The name of the loadset.

Explanation: The ZDMAP command was entered with the LOADSET parameter specified for a specific loadset name, but the requested program is not in that loadset. Either the program name is valid but is not in the specified loadset or the loadset is valid but does not contain the specified program.

System Action: No link map data is displayed.

User Response: Do the following:

  1. Enter ZOLDR DISPLAY PROG specifying the program name. This will show the loadsets, if any, in which that program is contained.
  2. Enter the ZDMAP command again with the LOADSET parameter specifying the name of the loadset that contains the program for which you want to display link map data.

See TPF Operations for more information about the ZDMAP and ZOLDR DISPLAY commands.

DMAP2011EPROGRAM progname IS EXCLUDED FROM LOADSET lsname. CANNOT PROCESS ZDMAP REQUEST.

Where:

progname
The name of the program.

lsname
The name of the loadset.

Explanation: The ZDMAP command was entered with the LOADSET parameter specified for a specific loadset name to display link map data for a program. However, the program has been excluded from the loadset.

System Action: No link map data is displayed.

User Response: Do the following:

  1. Do one of the following:
  2. Enter the ZOLDR REINCLUDE command to restore the program to the loadset.
  3. Enter the ZOLDR ACTIVATE command to activate the loadset.
  4. Enter the ZDMAP command again with the LOADSET parameter specifying the loadset name.

See TPF Operations for more information about the ZDMAP, ZOLDR ACTIVATE, ZOLDR DEACTIVATE, and ZOLDR REINCLUDE commands.

DMAP2012ELOADSET lsname IS NOT ACTIVE

Where:

lsname
The name of the loadset.

Explanation: The ZDMAP command was entered with the LOADSET parameter specified with a specific loadset name to display link map data for a program. However, the loadset is not active.

System Action: No link map data is displayed.

User Response: Do the following:

  1. Enter the ZOLDR ACTIVATE command to activate the loadset.
  2. Enter the ZDMAP command again with the LOADSET parameter specifying the loadset name.

See TPF Operations for more information about the ZDMAP and ZOLDR ACTIVATE commands.

DMAP2013ENO ACTIVE VERSIONS OF UNALLOCATED PROGRAM progname AVAILABLE HERE

Where:

progname
The name of the program.

Explanation: One of the following errors occurred:

System Action: No link map data is displayed.

User Response: Enter ZDPAT progname COPY-C (where progname is the program name) to display the versions of the program that are available and do one of the following:

See TPF Operations for more information about the ZDMAP, ZDPAT, and ZOLDR ACTIVATE commands.

DMAP2014EUNABLE TO LOCK PROGRAM prognamevv IN LOADSET lsnameb INTO MAIN STORAGE. CANNOT PROCESS ZDMAP REQUEST. GETPC RETURN CODE - rc

Where:

prognamevv
The name and version of the program.

lsnameb
The name of the loadset or BASE.

rc
The return code from the getpc function.

Explanation: One of the following errors occurred:

System Action: No link map data is displayed.

User Response: Determine the cause of the problem and do one of the following:

See TPF Operations for more information about the ZDMAP and ZCTKA commands. See the TPF C/C++ Language Support User's Guide for more information about the return codes from the getpc function. See TPF System Installation Support Reference for more information about loaders.

DMAP2015EUNEXPECTED GETPC ERROR FOR PROGRAM progname. CANNOT PROCESS ZDMAP REQUEST. GETPC RETURN CODE - rc

Where:

progname
The name of the program.

rc
The return code from the getpc function.

Explanation: The ZDMAP command was entered without the LOADSET parameter specified. ZDMAP processing issued the getpc function to determine which version of the program to display and getpc returned with an error. Because the getpc function was issued with NO_LOCK specified, this error is unexpected.

System Action: No link map data is displayed.

User Response: Have your system programmer determine the cause of the error and correct it.

See TPF Operations for more information about the ZDMAP command. See the TPF C/C++ Language Support User's Guide for more information about the return codes from the getpc function.

DMAP3000EC LOAD MODULE ccccvv IN LOADSET lsnameb CONTAINS NO LINK MAP DATA

Where:

ccccvv
The name and version of the C load module.

lsnameb
The name of the loadset or BASE.

Explanation: This error occurs in response to a ZDMAP command when the C load module specified does not contain any link map data.

System Action: No link map data is displayed.

User Response: Do the following:

  1. Rebuild the C load module offline so that it contains link map data.
  2. Reload the C load module.

See TPF Application Programming for more information about including link map data when building C load modules. See TPF Operations for more information about the ZDMAP command.

DMAP3001ENO MATCH FOUND IN C LOAD MODULE ccccvv IN LOADSET lsnameb FOR OBJECT FILE objname

Where:

ccccvv
The name and version of the C load module.

lsnameb
The name of the loadset or BASE.

objname
The name of the requested object file.

Explanation: This error occurs when the object file name specified with the ZDMAP command is not found in the specified C load module.

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP command.

DMAP3002ENO MATCH FOUND IN C LOAD MODULE ccccvv IN LOADSET lsnameb FOR FUNCTION funcname

Where:

ccccvv
The name and version of the C load module.

lsnameb
The name of the loadset or BASE.

funcname
The name of the requested function.

Explanation: This error occurs when the function name specified with the ZDMAP command is not found in the specified C load module.

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP command.

DMAP3003EADDRESS address IS NOT IN C LOAD MODULE ccccvv IN LOADSET lsnameb

Where:

address
The hexadecimal address entered with the ADDRESS parameter of the ZDMAP command.

ccccvv
The name and version of the C load module.

lsnameb
The name of the loadset or BASE.

Explanation: One of the following errors occurred:

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP and ZRPGM commands.

DMAP3004ENOT ENOUGH MALLOC STORAGE AVAILABLE TO PROCESS ALL LINK MAP DATA FOR C LOAD MODULE ccccvv

Where:

ccccvv
The name and version of the C load module.

Explanation: While processing the ZDMAP command, there was not enough storage available to fully process the request for all the link map data requested.

System Action: No link map data is displayed.

User Response: Do one of the following:

See TPF Operations for more information about the ZDMAP command.

DMAP3005EC LOAD MODULE ccccvv IN LOADSET lsnameb CONTAINS LINK MAP DATA THAT CANNOT BE RECOGNIZED. CANNOT PROCESS ZDMAP REQUEST.

Where:

ccccvv
The name and version of the C load module.

lsnameb
The name of the loadset or BASE.

Explanation: This error occurs in response to a ZDMAP command when the C load module specified contains link map data that is in a format that is not recognized by the ZDMAP command.

System Action: No link map data is displayed.

User Response: Do the following:

  1. Rebuild the C load module offline so that it contains link map data in a recognized format.
  2. Reload the C load module.

See TPF Application Programming for more information about including link map data when building C load modules. See TPF Operations for more information about the ZDMAP command.

DMFS0005Ihh.mm.ss

Where:

hh
The hour.

mm
The minute.

xx
The second.

Explanation: This is the normal response to the ZDMFS DISPLAY command. This message displays the module numbers, error counts, and lock status.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDMFS command and an example of the informational display.

DMFS0006Imod AND FOLLOWING MODS OFFLINE

Where:

mod
The module name.

Explanation: The ONLINE option is specified in the ZDMFS command when the requested module and all following modules are offline.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDMFS and ZSONS commands.

DMFS0054EINVALID STARTING MODULE NUMBER

Explanation: The specified starting module number is:

It can be accessed only by specifying pseudo numbers in the ZDMFS command.

System Action: None.

User Response: If you are not certain that the last displayed module number represents the largest valid module number in the installation, increase the last module number by one and enter it as the starting module number in a subsequent request. The program responds with the DMFS0054E error message. For example, you can specify the starting module number 0F1 in the ZDMFS command. The highest valid module number in the installation is 0F2. The limit of output lines is 5. Only two lines are printed since symbolic, or pseudo module number, 0F3 does not exist in the particular installation.

See TPF Operations for more information about the ZDMFS and ZSONS commands.

DNSC0001EERROR ALLOCATING IDNSHOSTADDR CACHE

Explanation: There is not enough contiguous system heap storage available to obtain the amount requested for the IDNSHOSTADDR Domain Name System (DNS) client cache.

System Action: The TPF system will call the external DNS server for all gethostbyaddr() function calls.

User Response: Do one of the following:

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support. See TPF Operations for more information about the ZCACH and ZCTKA ALTER commands and increasing system heap storage.

DNSC0002IIDNSHOSTADDR CLIENT CACHE INITIALIZED

Explanation: The TPF Domain Name System (DNS) client cache, which saves remote Internet protocol (IP) addresses and their corresponding remote host names, has been initialized.

System Action: None.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSC0003EERROR ALLOCATING IDNSHOSTNAME CACHE

Explanation: There is not enough contiguous system heap storage available to obtain the amount requested for the IDNSHOSTNAME Domain Name System (DNS) client cache.

System Action: The TPF system will call the external DNS server for all gethostbyname() function calls.

User Response: Do one of the following:

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support. See TPF Operations for more information about the ZCACH and ZCTKA ALTER commands and increasing system heap storage.

DNSC0004IIDNSHOSTNAME CLIENT CACHE INITIALIZED

Explanation: The TPF Domain Name System (DNS) client cache, which saves remote host names and their corresponding Internet protocol (IP) addresses, has been initialized.

System Action: None.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSC0005ESYSTEM HEAP NOT OBTAINED, name TABLE NOT CREATED

Where:

name
The name of a file containing external host names and associated IP addresses, which may be used to resolve gethostbyaddr() or gethostbyname() function calls.

Explanation: An attempt was made to create the TPF external host name table by writing the file to system heap storage. However, there was not enough contiguous system heap storage available to obtain the amount requested.

System Action: The TPF system will not use the file to resolve gethostbyaddr() or gethostbyname() function calls, but will resolve the function calls by calling the Domain Name System (DNS) external server or by reading the data from the IDNSHOSTADDR DNS client cache for gethostbyaddr() function calls or from the IDNSHOSTNAME DNS client cache for gethostbyname() function calls.

User Response: Do the following:

  1. Enter the ZCTKA ALTER command to increase the amount of system heap storage.
  2. IPL the TPF system.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support. See TPF Operations for more information about the ZCTKA ALTER command and increasing system heap storage.

DNSC0006ESYSTEM HEAP NOT OBTAINED, name TABLE NOT REFRESHED

Where:

name
The name of a file containing external host names and associated IP addresses, which may be used to resolve gethostbyaddr() or gethostbyname() function calls.

Explanation: An attempt was made to refresh the TPF external host name table by writing the file to system heap storage. However, there was not enough contiguous system heap storage available to obtain the amount requested.

System Action: The TPF external host name table in system heap storage is not changed.

User Response: Do the following:

  1. Enter the ZCTKA ALTER command to increase the amount of system heap storage.
  2. IPL the TPF system.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support. See TPF Operations for more information about the ZCTKA ALTER command.

DNSC0007Ename TABLE NOT CREATED, LAST VALID HOST NAME IS hostname

Where:

name
The name of a file containing external host names and associated IP addresses, which may be used to resolve gethostbyaddr() or gethostbyname() function calls.

hostname
The last valid host name in the file.

Explanation: An attempt was made to create the TPF external host name table by writing the file to system heap storage. However, the TPF system detected an error while parsing the file. The last valid host name in the file is displayed.

System Action: The TPF system will not use the TPF external host name table to resolve gethostbyaddr() or gethostbyname() function calls, but will resolve the function calls by calling the Domain Name System (DNS) external server or by reading the data from the IDNSHOSTADDR DNS client cache for gethostbyaddr() function calls or from the IDNSHOSTNAME DNS client cache for gethostbyname() function calls.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSC0008Ename TABLE NOT REFRESHED, LAST VALID HOST NAME IS hostname

Where:

name
The name of a file containing host names and associated Internet Protocol (IP) addresses, which may be used to resolve gethostbyaddr() or gethostbyname() function calls.

hostname
The last valid host name in the file.

Explanation: An attempt was made to refresh the TPF external host name table by writing the updated file to system heap storage. However, the TPF system detected an error while parsing the file. The last valid host name in the file is displayed.

System Action: The TPF external host name table in system heap storage is not changed.

User Response: Create a valid Domain Name System (DNS) host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSC0009Ename TABLE NOT CREATED, LAST VALID HOST NAME FOUND

Where:

name
The name of a file containing host names and associated Internet Protocol (IP) addresses, which may be used to resolve gethostbyaddr() or gethostbyname() function calls.

Explanation: An attempt was made to create the TPF external host name table by writing the file to system heap storage. However, the TPF system detected an error while parsing the file.

System Action: The TPF system will not use the TPF external host name table to resolve gethostbyaddr() or gethostbyname() function calls, but will resolve the function calls by calling the Domain Name Server (DNS) external server or by reading the data from the IDNSHOSTADDR DNS client cache for gethostbyaddr() function calls or from the IDNSHOSTNAME DNS client cache for gethostbyname() function calls.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSC0010Ename TABLE NOT REFRESHED, NO VALID HOST NAME FOUND

Where:

name
The name of a file containing external host names and associated Internet Protocol (IP) addresses, which may be used to resolve gethostbyaddr() or gethostbyname() function calls.

Explanation: An attempt was made to refresh the TPF external host name table by writing the file to system heap storage. However, the TPF system detected an error while parsing the file.

System Action: The TPF system will not use the TPF external host name table to resolve gethostbyaddr() or gethostbyname() function calls, but will resolve the function calls by calling the Domain Name System (DNS) external server or by reading the data from the IDNSHOSTADDR DNS client cache for gethostbyaddr() function calls or from the IDNSHOSTNAME DNS client cache for gethostbyname() function calls.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSC0011Iname FILE HAS BEEN WRITTEN TO SYSTEM HEAP

Where:

name
The name of a file containing external host names and associated IP addresses, which may be used to resolve gethostbyaddr() or gethostbyname() function calls.

Explanation: The file has been written to system heap storage.

System Action: None.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0001EDNS SERVER HOSTNAME TABLE NOT REFRESHED LAST VALID HOSTNAME IN FILE name IS host name

Where:

name
The name of the Domain Name System (DNS) server host name file.

host name
The first 40 characters of the last host name that was successfully processed from the DNS host name file.

Explanation: An attempt was made to refresh the TPF host name table in system heap storage with data from an updated file. However, an error occurred during the process. The last host name that was successfully processed from the DNS host name file is displayed.

System Action: The host name table in system heap storage is not changed.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0002EDNS SERVER FILE name DOES NOT EXIST

Where:

name
The name of the Domain Name System (DNS) server host name file.

Explanation: An attempt was made to copy the TPF host name file to system heap, but the host name file does not exist.

System Action: The DNS server host name table, if already created in system heap storage, is not changed.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0003EDNS SERVER HOSTNAME TABLE NOT REFRESHED FIRST HOSTNAME IN FILE name IS NOT VALID

Where:

name
The name of the Domain Name System (DNS) server host name file.

Explanation: An attempt was made to refresh the TPF host name table in system heap storage with data from an updated file. However, an error occurred on the first host name in the file.

System Action: The host name table in system heap storage is not changed.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0004IDNS SERVER HOSTNAME TABLE REFRESH COMPLETED

Explanation: The Domain Name System (DNS) server host name table was refreshed in system heap.

System Action: None.

User Response: None.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0005EDNS SERVER ERROR OPENING FILE name ERRNO description

Where:

name
The name of the Domain Name System (DNS) server host name file.

description
The errno function value.

Explanation: An error occurred when trying to open the DNS server host name file located in the TPF file system.

System Action: The DNS server host name table, if already created in system heap storage, is not changed.

User Response: Look in errno.h to see a description of the error and do one of the following:

See TPF Operations for more information about the ZFILE chmod command. See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0006EDNS SERVER HOSTNAME TABLE NOT CREATED FIRST HOSTNAME IN FILE name IS NOT VALID

Where:

name
The name of the Domain Name System (DNS) server host name file.

Explanation: An attempt was made to initialize the TPF host name table in system heap storage with data from an updated file. However, an error occurred on the first host name in the file.

System Action: The DNS server host name table is not created in system heap.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0007EDNS SERVER HOSTNAME TABLE NOT REFRESHED ERROR ALLOCATING SYSTEM HEAP

Explanation: An attempt was made to refresh the TPF host name table in system heap storage from an updated file. However, there is not enough contiguous system heap storage available to obtain the amount requested.

System Action: The host name table in system heap storage is not changed.

User Response: Do the following:

  1. Enter the ZCTKA ALTER command to increase the amount of system heap storage.
  2. IPL the TPF system.

See TPF Operations for more information about the ZCTKA ALTER command and increasing system heap storage. See TPF Transmission Control Protocol/Internet Protocol for more information about Domain Name System (DNS) support.

DNSS0008EDNS SERVER HOSTNAME TABLE NOT CREATED ERROR ALLOCATING SYSTEM HEAP

Explanation: An attempt was made to create the DNS server host name table in system heap storage from the DNS server host name file, /etc/host.txt, in the TPF file system. However, there was not enough contiguous system heap storage available to obtain the amount requested.

System Action: The Domain Name System (DNS) server host name table is not created in system heap storage.

User Response: Do the following:

  1. Enter the ZCTKA ALTER command to increase the amount of system heap storage.
  2. IPL the TPF system.

See TPF Operations for more information about the ZCTKA ALTER command and increasing system heap storage. See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0009EDNS SERVER HOSTNAME TABLE NOT CREATED LAST VALID HOSTNAME IN FILE name IS host name

Where:

name
The name of the Domain Name System (DNS) server host name file.

host name
The first 40 characters of the last host name that was successfully processed from the DNS host name file.

Explanation: An attempt was made to copy the TPF host name table to system heap storage from a file in the TPF file system. However, an error occurred during the process. The last valid host name in the file is displayed.

System Action: The TPF DNS server is stopped.

User Response: Create a valid DNS host name file.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0010EDNS SERVER IS ONLY ALLOWED TO RUN FROM THE BSS

Explanation: An attempt was made to start the Domain Name System (DNS) server from a subsystem other than the basic subsystem (BSS).

System Action: The TPF DNS server is stopped.

User Response: Do the following:

  1. Enter the ZINET DELETE command from the other subsystem to remove the DNS server entry for the Internet daemon (INETD) table of that subsystem.
  2. Enter the ZINET ADD command from the BSS to define the DNS server to the BSS INETD table.
  3. Enter the ZINET START command from the BSS to activate the DNS server.

See TPF Operations for more information about the ZINET commands. See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0011EDNS SERVER ERROR ON RECVFROM ERRNO error_number

Where:

error_number
The value of the sock_errno() function.

Explanation: An error occurred when a recvfrom() function attempted to read a Domain Name System (DNS) query.

System Action: The DNS server socket is closed and Internet daemon (INETD) processing restarts the DNS server.

User Response: See socket.h for a description of the error number value.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0012EDNS SERVER HOSTNAME TABLE DOES NOT EXIST

Explanation: The Domain Name System (DNS) server has detected that the DNS server host name table has not been created.

System Action: The TPF DNS server is stopped.

User Response: Do one of the following:

See TPF Operations for more information about the ZCTKA ALTER command and how to increase system heap storage. See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0013IDNS SERVER HOST NAME TABLE INITIALIZATION COMPLETED

Explanation: The TPF host name table was initialized from the Domain Name System (DNS) server host name file.

System Action: None.

User Response: None

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.

DNSS0015EDNS SERVER MUST HAVE INETD SERVER NAME SET TO DNS

Explanation: The Domain Name System (DNS) server detected that a server entry with a name other than DNS (the only supported server name) was defined for the Internet daemon (INETD).

System Action: The TPF DNS server is stopped.

User Response: Do the following:

  1. Enter the ZINET DELETE command to delete the incorrect INETD entry.
  2. Enter the ZINET ADD command using DNS as the server name.
  3. Enter the ZINET START command to start the DNS server again.

See TPF Transmission Control Protocol/Internet Protocol for more information about offload and native stack support. See TPF Operations for more information about the ZINET commands.

DNSS0016EDNS SERVER ERROR READING FILE name ERRNO description

Where:

name
The name of the Domain Name System (DNS) server host name file.

description
The errno function value.

Explanation: An attempt was made to read a file in the TPF file system, but the TPF system could not access the file.

System Action: The TPF DNS server is not started.

User Response: Have your system programmer determine the cause of the problem and correct the error.

See TPF Transmission Control Protocol/Internet Protocol for more information about DNS support.