 |
Publication changes for APARs OA25593 and PK68195
|
| | | Abstract | APARs OA25593 and PK68195 collectively provide support for the Migration Health Checker for Communication Server function that checks for functions which will be removed in a future release of z/OS Communication Server. This includes the following functions that Statement of Directions (SODs) have been issued for:
1. Boot Information Negotiation Layer (BINL)
2. Berkeley Internet Name Domain (BIND) 4.9.3
3. Dynamic Host Configuration Protocol (DHCP)
4. Network Database (NDB)
This technote documents the associated changes to z/OS V1R8 and z/OS V1R9 Communications Server and Health Checker publications. | | | | | | Content | Title: z/OS Comm Svr: New Function Summary
Release: z/OS V1R8 and V1R9
Document Number: GC31-8771-02 GC31-8771-03
In the IP section: Add the following new function:
IBM Health Checker for z/OS enhancements
IBM Health Checker for z/OS is a z/OS component that installations can use to gather information about their system environment and system parameters to help identify potential configuration problems before they impact availability or cause outages. Individual products, z/OS components, or Independent Software Vendor (ISV) software can provide checks that take advantage of the IBM Health Checker for z/OS framework.
In a future release of z/OS, support for several functions is planned to be discontinued. z/OS V1R8, V1R9, and V1R10 Communications Server provide four new IBM Health Checker for z/OS checks to help you determine whether selected Communications Server functions are active on your current systems:
- Boot Information Negotiation Layer (BINL) server
- Berkeley Internet Name Domain 4.9.3 (BIND 4.9.3) DNS server
- Dynamic Host Configuration Protocol (DHCP) server
- Network Database (NDB) server
If you are using these functions, you are encouraged to migrate by finding replacement or alternative processes.
See z/OS Migration updates in this document for detailed information about these functions, including the steps you should take to migrate to using replacement functions.
Dependencies for the IBM Health Checker for z/OS enhancements
You must start the IBM Health Checker for z/OS before you can use the IBM Health Checker for z/OS enhancements.
Using the IBM Health Checker for z/OS enhancements
If you want to use these enhancements, perform the appropriate tasks in table.
Table: IBM Health Checker for z/OS enhancements
| Task | Procedure | Reference | | Use the IBM Health Checker for z/OS migration check support. | Perform the following steps:
- Configure and start the IBM
Health Checker for z/OS.
- Review check output for
potential migration actions. | See the following topics in IBM Health
Checker for z/OS: User's Guide: |
Title: z/OS Migration
Release: z/OS V1R8 and V1R9
Document Number: GA22-7499-10 GA22-7499-12
Add the following Communications Server actions to perform before installing OA25593:
IP Services: Migrate from NDB function
Description: z/OS V1R10 is planned to be the last release in which z/OS Communications Server supports the Network Database (NDB) function. After z/OS V1R10, the function will be removed from z/OS.
| Element or feature: | Communications Server. | | When change was introduced: | Removal of support effective with an unspecified future release was announced on 7 August 2007 in the z/OS V1R9 availability announcement. Removal of support effective with the release following z/OS V1R10 was announced on 26 February 2008 in the z/OS V1R10 preview announcement. | | Applies to migration from: | None. | | Timing: | None. | | Is the migration action required? | No, but recommended if you use the NDB function because the action is planned to become a requirement in the release following z/OS V1R10. | | Target system hardware requirements: | None. | | Target system software requirements: | None. | | Other system (coexistence or fallback) requirements: | None. | | Restrictions: | None. | | System impacts: | None. |
Steps to take: Change your processes to use the distributed data facility (DDF) provided by DB2 for z/OS, and the DB2 Runtime Client. DDF allows client applications running in an environment that supports Distributed Relational Database Architecture(TM) (DRDA(R)) to access data at DB2 servers.
Tip: Use IBM Health Checker for z/OS to determine if the NDB function is in use. The check is named ZOSMIGV1R10_CS_NDB.
Reference information: For an introduction to the distributed data facility of z/OS for DB2, see Introduction to DB2 for z/OS, SC18-9847-00.
IP Services: Migrate from BIND DNS 4.9.3 function
Description: z/OS V1R10 is planned to be the last release in which z/OS Communications Server supports BIND DNS 4.9.3. After z/OS V1R10, the function will be removed from z/OS.
| Element or feature: | Communications Server. |
|---|
| When change was introduced: | The removal of BIND DNS 4.9.3 function was announced in October 2003. At that time, z/OS V1R7 was planned to be the last release in which the function would be available. Subsequently, the removal was delayed, and now z/OS V1R10 is planned to be the last release in which the function is available, as stated in the 26 February 2008 z/OS V1R10 preview announcement. | | Applies to migration from: | None. | | Timing: | None. | | Is the migration action required? | No, but recommended if you use BIND DNS 4.9.3 function because the action is planned to become a requirement in the release following z/OS V1R10. | Target system hardware
requirements: | None. | Target system software
requirements: | None. | Other system (coexistence
or fallback) requirements: | None. | | Restrictions: | None. | | System impacts: | None. |
Steps to take: You should implement BIND DNS 9.2.0 as a replacement. BIND DNS 9.2.0 is included in z/OS beginning with V1R4. If you exploit the Connection Optimization (DNS/WLM) feature of BIND 4.9.3, you should investigate alternative solutions. One alternative would be using the sysplex distributor function, which is implemented using distributed dynamic VIPAs (VIPADISTRIBUTE statement in the TCPIP PROFILE). Another alternative is the z/OS Load Balancing Advisor in combination with the Automated Domain Name Registration application (ADNR), which provides the ability to automatically update DNS with the availability status of sysplex resources.
Tip: Use IBM Health Checker for z/OS to determine if the BIND DNS 4.9.3 function is in use. The check is named ZOSMIGV1R10_CS_BIND4.
Reference information: For information about setting up the BIND 9.2.0 name server, z/OS Load Balancing Advisor, or ADNR, see z/OS Communications Server: IP Configuration Guide and z/OS Communications Server: IP Configuration reference.
IP Services: Migrate from BINL function
Description: z/OS V1R10 is planned to be the last release in which z/OS Communications Server supports the Boot Information Negotiation Layer (BINL). After z/OS V1R10, the function will be removed from z/OS.
| Element or feature: | Communications Server. | | When change was introduced: | Removal of support effective with an unspecified future release was announced on 7 August 2007 in the z/OS V1R9 availability announcement. Removal of support effective with the release following z/OS V1R10 was announced on 26 February2008 in the z/OS V1R10 preview announcement. | | Applies to migration from: | None. | | Timing: | None. | | Is the migration action required? | No, but recommended if you use the BINL function because the action is planned to become a requirement in the release following z/OS V1R10. | Target system hardware
requirements: | None. | Target system software
requirements: | None. | Other system (coexistence or
fallback) requirements: | None. | | Restrictions: | None. | | System impacts: | None. |
Steps to take: Consider using the product IBM Tivoli(R) Provisioning Manager for OS Deployment V5 (5724-Q99) for network-based operating system installation services.
Tip: Use IBM Health Checker for z/OS to determine if the BINL function is in use. The check is named ZOSMIGV1R10_CS_BINL.
Reference information: For more information, see IBM Tivoli Provisioning Manager for OS Deployment Users Guide, SC32-2582.
IP Services: Migrate from DHCP server function
Description: z/OS V1R10 is planned to be the last release in which z/OS Communications Server supports the Dynamic Host Configuration Protocol (DHCP) server function. After z/OS V1R10, the function will be removed from z/OS.
| Element or feature: | Communications Server. | | When change was introduced: | Removal of support effective with a future release was announced on 7 August 2007 in the z/OS V1R9 availability announcement. Removal of support effective with the release following z/OS V1R10 was announced on 26 February 2008 in the z/OS V1R10 preview announcement. | | Applies to migration from: | None. | | Timing: | None. | | Is the migration action required? | No, but recommended if you use the DHCP server because the action is planned to become a requirement in the release following z/OS V1R10. | Target system hardware
requirements: | None. | Target system software
requirements: | None. | Other system (coexistence or
fallback) requirements: | None. | | Restrictions: | None. | | System impacts: | None. |
Steps to take: You should implement the DHCP server on a system other than your z/OS system. If you want to continue to run the DHCP server on your System z hardware, you can implement a DHCP server inside a Linux for System z image. DHCP servers are widely available on a variety of platforms.
Tip: Use IBM Health Checker for z/OS to determine if the DHCP function is in use. The check is named ZOSMIGV1R10_CS_DHCP.
Reference information: For information about implementing a DHCP server on a non-z/OS system, refer to the documentation for that system.
Title: z/OS Comm Svr: IP Diagnosis Guide
Release: z/OS V1R8 and V1R9
Document Number: GC31-8782-07 GC31-8782-08
In the Appendix D. IBM Health Checker for z/OS, add Migration Health Checks after TCP/IP checks:
z/OS Communications Server TCP/IP provides the following migration health checks:
ZOSMIGV1R10_CS_BIND4
Checks whether the Berkeley Internet Name Domain 4.9.3 (BIND 4.9.3) DNS server function is in use on the system. By default this check is inactive. This default can be overridden on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. If an IBM Health Checker for z/OS exception message is generated then a migration action needs to be put in place before migrating to a release higher than z/OS V1R10.
ZOSMIGV1R10_CS_BINL
Checks whether the Boot Information Negotiation Layer (BINL) server function is in use on the system. By default this check is inactive. This default can be overridden on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. If an IBM Health Checker for z/OS exception message is generated then a migration action needs to be put in place before migrating to a release higher than z/OS V1R10.
ZOSMIGV1R10_CS_DHCP
Checks whether the Dynamic Host Configuration Protocol (DHCP) server function is in use on the system. By default this check is inactive. This default can be overridden on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. If an IBM Health Checker for z/OS exception message is generated then a migration action needs to be put in place before migrating to a release higher than z/OS V1R10.
ZOSMIGV1R10_CS_NDB
Checks whether the Network Database (NDB) server function is in use on the system. By default this check is inactive. This default can be overridden on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. If an IBM Health Checker for z/OS exception message is generated then a migration action needs to be put in place before migrating to a release higher than z/OS V1R10.
Title: z/OS Comm Svr: SNA Messages
Release: z/OS V1R8 and V1R9
Document Number: SC31-8790-06 SC31-8790-07
Add the new chapter for ISTM messages for Migration Health Checker as follows:
ISTM messages for Migration Health Checker
This chapter lists the messages beginning with ISTM. These messages are issued by IBM Migration Health Checker for z/OS.
___________________________________________________________________________________
ISTM001I BINL server function is not in use on this system.
Explanation:
Check ZOSMIGV1R10_CS_BINL ran successfully and found no exceptions. The check determined that the Boot Information Negotiation Layer (BINL) server function is not in use on this system. IBM has indicated in statements of direction that the BINL server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Not applicable.
User response:
Not applicable.
System programmer response:
Not applicable.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
Not applicable.
Automation:
Not applicable.
_______________________________________________________________________________________________
ISTM002E BINL server function is in use on this system during this IPL.
Explanation:
Check ZOSMIGV1R10_CS_BINL determined that the Boot Information Negotiation Layer (BINL) server function is in use on this system during this IPL. IBM has indicated in statements of direction that the BINL server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
This exception will continue to be reported for the duration of this IPL, or as long as this Migration Health Check is active. When this exception condition is detected, this message is issued and is followed by message ISTM900I, which indicates the date and time that the BINL server was last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the BINL server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of BINL server being active.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Contact the system programmer.
User response:
Not applicable.
System programmer response:
Since the BINL server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use the BINL server should investigate the use of IBM Director and Remote Deployment Manager (Tivoli(R) Provisioning Manager for OS Deployment Director Extension) for network based operating system installation services.
For mor information on the BINL server see the Boot Information Layer, Configuring BINL server topic section of z/OS Communication Server: IP Configuration Guide. For more information on the replacement functions, please refer to IBM Tivoli Provisioning Manager for OS Deployment product.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
12
Automation:
Not applicable.
___________________________________________________________________________________
ISTM003I BIND 4.9.3 DNS server function is not in use on this system.
Explanation:
Check ZOSMIGV1R10_CS_BIND4 ran successfully and found no exceptions. The check determined that the Berkeley Internet Name Domain 4.9.3 (BIND 4.9.3) DNS server function is not in use on this system. IBM has indicated in statements of direction that the BIND 4.9.3 server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Not applicable.
User response:
Not applicable.
System programmer response:
Not applicable.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
Not applicable.
Automation:
Not applicable.
_____________________________________________________________
ISTM004E BIND 4.9.3 DNS server function is in use on this system during this IPL.
Explanation:
Check ZOSMIGV1R10_CS_BIND4 determined that the Berkeley Internet Name Domain 4.9.3 (BIND 4.9.3) DNS server function is in use on this system during this IPL. IBM has indicated in statements of direction that the BIND 4.9.3 DNS server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
This exception will continue to be reported for the duration of this IPL, or as long as this Migration Health Check is active. When this exception condition is detected, this message is issued and is followed by message ISTM900I, which indicates the date and time that the BIND 4.9.3 DNS server had been last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the BIND 4.9.3 DNS server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of BIND 4.9.3 DNS server being active.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Contact the system programmer.
User response:
Not applicable.
System programmer response:
Since BIND 4.9.3 DNS server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use BIND 4.9.3 DNS server implement the BIND 9.2.0 DNS server as a replacement. Customers that use the load balancing Connection Optimization (DNS/WLM) feature of BIND 4.9.3 DNS server should investigate Sysplex Distributor, the Load Balancing Advisor (LBA), Automated Domain name Registration (ADNR), or other load balancing solutions.
See the information about the domain name system and workload balancing in z/OS Communication Server: IP Configuration Guide for more information on BIND 4.9.3 and BIND 9 DNS servers, Automated Domain name Registration (ADNR) and Load Balancing Advisor (LBA).
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
12
Automation:
Not applicable.
___________________________________________________________________________________
ISTM005I DHCP server function is not in use on this system.
Explanation:
Check ZOSMIGV1R10_CS_DHCP ran successfully and found no exceptions. The check determined that the Dynamic Host Configuration Protocol (DHCP) server function is not in use on this system. IBM has indicated in statements of direction that the DHCP server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Not applicable.
User response:
Not applicable.
System programmer response:
Not applicable.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
Not applicable.
Automation:
Not applicable.
___________________________________________________________________________________
ISTM006E DHCP server function is in use on this system during this IPL.
Explanation:
Check ZOSMIGV1R10_CS_DHCP determined that the Dynamic Host Configuration Protocol (DHCP) server function is in use on this system during this IPL. IBM has indicated in statements of direction that the DHCP server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
This exception will continue to be reported for the duration of this IPL, or as long as this Migration Health Check is active. When this exception condition is detected, this message is issued and is followed by message ISTM900I which indicates the date and time that the DHCP server had been last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the DHCP server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of DHCP server being active.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Contact the system programmer.
User response:
Not applicable.
System programmer response:
Since DHCP server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use DHCP server should investigate using a DHCP server on Linux for System z(TM).
For more information on the DHCP server, see the Configuring the DHCP server for z/OS topic section of z/OS Communication Server: IP Configuration Guide. For more information on the replacement functions, please refer to the DHCP server on Linux for System z product.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
12
Automation:
Not applicable.
______________________________________________________________________________________________
ISTM007I NDB server function is not in use on this system.
Explanation:
Check ZOSMIGV1R10_CS_NDB ran successfully and found no exceptions. The check determined that the Network Database System (NDB) server function is not in use on this system. IBM has indicated in statements of direction that the NDB server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Not applicable.
User response:
Not applicable.
System programmer response:
Not applicable.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
Not applicable.
Automation:
Not applicable.
___________________________________________________________________________________
ISTM008E NDB server function is in use on this system during this IPL.
Explanation:
Check ZOSMIGV1R10_CS_NDB determined that the Network Database System (NDB) server function is in use on this system during this IPL. IBM has indicated in statements of direction that the NDB server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
This exception will continue to be reported for the duration of this IPL, or as long as this Migration Health Check is active. When this exception condition is detected, this message is issued and is followed by message ISTM900I which indicates the date and time that the NDB server had been last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the NDB server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of NDB server being active.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Contact the system programmer.
User response:
Not applicable.
System programmer response:
Since NDB server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use the NDB server should investigate the distributed data facility (DDF) provided by z/OS DB2(R), and the DB2 Run-Time Client. DDF allows client applications running in an environment that supports DRDA(R) to access data at DB2 servers.
For more information on the NDB server, see the remote procedure calls chapter of z/OS Communication Server: IP Configuration Guide. For more information on the replacement functions, please refer to Distributed Data Facility (DDF) in the DB2 product.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
12
Automation:
Not applicable.
_______________________________________________________________________________________________
ISTM900I Function: mhc_function last started on mhc_date at mhc_time.
Explanation:
A preceding Health Checker exception message of type ISTMxxxE was generated. See those messages for more information.
In the message text:
mhc_function
The name of the function that was being checked.
mhc_date
The date that the function was last started.
mhc_time
The time that the function was last started.
Example:
Not applicable.
System action:
The system continues processing.
Operator response:
Not applicable.
User response:
Not applicable.
System programmer response:
Not applicable.
Problem determination:
Not applicable.
Source:
z/OS Communications Server Health Checker
Module:
ISTHCCK2
Routing code:
Not applicable.
Descriptor code:
Not applicable.
Automation:
Not applicable.
Title: IBM Health Checker for z/OS User's Guide
Release: z/OS V1R8 and V1R9
Document Number: SA22-7994-04 SA22-7994-06
In chapter: 'IBM Health Checker for z/OS checks',
'Communication Server checks (IBMCS)',
Add the following Migration Health Checks:
ZOSMIGV1R10_CS_BIND4
Description:
Checks whether the Berkeley Internet Name Domain 4.9.3 (BIND 4.9.3) DNS server is in use on this system. IBM has indicated in statements of direction that the BIND 4.9.3 DNS server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
If this check determines that the BIND 4.9.3 DNS server is in use, it will continue to report this exception for the duration of this IPL, or as long as this migration health check is active. When this exception condition is detected, message ISTM004E will be issued and will be followed by message ISTM900I which will indicate the date and time that the BIND 4.9.3 DNS server had been last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the BIND 4.9.3 DNS server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of BIND 4.9.3 DNS server being active.
This check will be processed shortly after VTAM initialization. At that point the BIND 4.9.3 DNS server may have not been started yet. As a result, you may not see an exception for this check the first time the check is processed even if you are running the BIND 4.9.3 DNS server on this system. However, subsequent processing of the check (manually triggered or during subsequent intervals) will detect whether the BIND 4.9.3 DNS server was started on this system.
Reason for check:
Since the BIND 4.9.3 DNS server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use BIND 4.9.3 DNS server implement the BIND 9.2.0 DNS server as a replacement. Customers who use the load balancing Connection Optimization (DNS/WLM) feature of BIND 4.9.3 DNS server should investigate Sysplex Distributor, the Load Balancing Advisor (LBA), Automated Domain name Registration (ADNR), or other load balancing solutions.
z/OS releases the check applies to:
z/OS V1R8, V1R9, and V1R10
User override of IBM values:
The following shows keywords you can use to override check values on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. This statement may be copied and modified to override the check defaults:
UPDATE
CHECK(IBMCS,ZOSMIGV1R10_CS_BIND4)
DATE(20070901)
REASON(’CHECK IF THE BIND 4.9.3 DNS SERVER IS IN USE’)
INACTIVE
SEVERITY(LOW)
INTERVAL(24:00)
Debug Support:
No
Verbose support:
No
Parameters accepted:
No
Reference:
See the following:
Messages:
This check issues the following exception messages:
See z/OS Communications Server, SNA Messages.
SECLABEL recommended for multilevel security (MLS) users: SYSLOW - See z/OS planning for Multilevel Security and the Common Criteria for information on using SECLABELs.
ZOSMIGV1R10_CS_BINL
Description:
Checks whether the Boot Information Negotiation Layer (BINL) server function is in use on this system. IBM has indicated in statements of direction that the BINL server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
If this check determines that the BINL server is in use, it will continue to report this exception for the duration of this IPL, or as long as this migration health check is active. When this exception condition is detected, message ISTM002E will be issued and will be followed by message ISTM900I which will indicate the date and time that the BINL server had been last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the BINL server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of BINL server being active.
This check will be processed shortly after VTAM initialization. At that point the BINL server may have not been started yet. As a result, you may not see an exception for this check the first time the check is processed even if you are running BINL server on this system. However, subsequent processing of the check (manually triggered or during subsequent intervals) will detect whether the BINL server was started on this system.
Reason for check:
Since BINL server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use BINL server should investigate the use of IBM Director and Remote Deployment Manager (Tivoli Provisioning Manager for OS Deployment Director Extension) for network based operating system installation services.
z/OS releases the check applies to:
z/OS V1R8, V1R9, and V1R10
User override of IBM values:
The following shows keywords you can use to override check values on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. This statement may be copied and modified to override the check defaults:
UPDATE
CHECK(IBMCS,ZOSMIGV1R10_CS_BINL)
DATE(20070901)
REASON(’CHECK IF THE BINL SERVER IS IN USE’)
INACTIVE
SEVERITY(LOW)
INTERVAL(24:00)
Debug Support:
No
Verbose support:
No
Parameters accepted:
No
Reference:
For more information on the BINL server, see the Configuring the BINL server in z/OS Communications Server : IP Configuration Guide .
For more information on the replacement functions, please refer to IBM Tivoli Provisioning Manager for OS Deployment product.
Messages:
This check issues the following exception messages:
See z/OS Communications Server, SNA Messages.
SECLABEL recommended for multilevel security (MLS) users: SYSLOW - See z/OS planning for Multilevel Security and the Common Criteria for information on using SECLABELs.
ZOSMIGV1R10_CS_DHCP
Description:
Checks whether the Dynamic Host Configuration Protocol (DHCP) server function is in use on this system. IBM has indicated in statements of direction that the DHCP server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
If this check determines that the DHCP server is in use, it will continue to report this exception for the duration of this IPL, or as long as this migration health check is active. When this exception condition is detected, message ISTM006E will be issued and will be followed by message ISTM900I which will indicate the date and time that the DHCP server had been last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the DHCP server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of DHCP server being active.
This check will be processed shortly after VTAM initialization. At that point the DHCP server may have not been started yet. As a result, you may not see an exception for this check the first time the check is processed even if you are running DHCP server on this system. However, subsequent processing of the check (manually triggered or during subsequent intervals) will detect whether the DHCP server was started on this system.
Reason for check:
Since DHCP server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use DHCP server should investigate using a DHCP server on Linux for System z.
z/OS releases the check applies to:
z/OS V1R8, V1R9, and V1R10
User override of IBM values:
The following shows keywords you can use to override check values on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. This statement may be copied and modified to override the check defaults:
UPDATE
CHECK(IBMCS,ZOSMIGV1R10_CS_DHCP)
DATE(20070901)
REASON(’CHECK IF THE DHCP SERVER IS IN USE’)
INACTIVE
SEVERITY(LOW)
INTERVAL(24:00)
Debug Support:
No
Verbose support:
No
Parameters accepted:
No
Reference:
For more information on the DHCP server, see the Configuring the DHCP server for z/OS in z/OS Communications Server : IP Configuration Guide .
For more information on the replacement functions, please refer to the DHCP server on Linux for System z product.
Messages:
This check issues the following exception messages:
See z/OS Communications Server, SNA Messages.
SECLABEL recommended for multilevel security (MLS) users: SYSLOW - See z/OS planning for Multilevel Security and the Common Criteria for information on using SECLABELs.
ZOSMIGV1R10_CS_NDB
Description:
Checks whether the Network Database System (NDB) server function is in use on this system. IBM has indicated in statements of direction that the NDB server will not be available in future IBM z/OS Communications Server releases after z/OS V1R10.
If this check determines that the NDB server is in use, it will continue to report this exception for the duration of this IPL, or as long as this migration health check is active. When this exception condition is detected, message ISTM008E will be issued and will be followed by message ISTM900I which will indicate the date and time that the NDB server had been last started, even if it is no longer active. Therefore, if this exception condition has been corrected (for example, the NDB server has been stopped and the configuration modified to use an alternative function) you can use message ISTM900I to determine whether a new instance of the server has been started or whether the exception condition is related to the earlier detection of NDB server being active.
This check will be processed shortly after VTAM initialization. At that point the NDB server may have not been started yet. As a result, you may not see an exception for this check the first time the check is processed even if you are running NDB server on this system. However, subsequent processing of the check (for example, manually triggered or during subsequent intervals) will detect whether the NDB server was started on this system.
Reason for check:
Since NDB server will no longer be supported in future releases after z/OS V1R10, IBM suggests that customers who currently use or plan to use the NDB server should investigate the Distributed Data Facility (DDF) provided by z/OS DB2, and the DB2 Run-Time Client. DDF allows client applications running in an environment that supports DRDA to access data at DB2 servers.
z/OS releases the check applies to:
z/OS V1R8, V1R9, and V1R10
User override of IBM values:
The following shows keywords you can use to override check values on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. This statement may be copied and modified to override the check defaults:
UPDATE
CHECK(IBMCS,ZOSMIGV1R10_CS_NDB)
DATE(20070901)
REASON(’CHECK IF THE NDB SERVER IS IN USE’)
INACTIVE
SEVERITY(LOW)
INTERVAL(24:00)
Debug Support:
No
Verbose support:
No
Parameters accepted:
No
Reference:
For more information on the NDB server, see the Remote Procedure Calls in z/OS Communications Server : IP Configuration Guide .
For more information on the replacement functions, please refer to Distributed Data Facility (DDF) in the DB2 product .
Messages:
This check issues the following exception messages:
See z/OS Communications Server, SNA Messages.
SECLABEL recommended for multilevel security (MLS) users: SYSLOW - See z/OS planning for Multilevel Security and the Common Criteria for information on using SECLABELs. | | | | | | | | |
|
|
| IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. |
|
|
|
|
| Please take a moment to complete this form to help us better serve you. |
|
 |
|
|
|
|
|
|
| Product categories: |
|
| | Software | |
| | Networking | |
| | Enterprise Connectivity | |
| | z/OS Communications Server | |
| | All | |
|
| Operating system(s): |
| |
z/OS
|
|
| Software version: |
| |
1.8, 1.9
|
|
| Reference #: |
| |
1313034
|
|
| IBM Group: |
| | Software Group |
|
| Modified date: |
| | 2009-07-21 |
|
|
