Beta Systems products with spool files will output a warning message when the number of available model spool files is too low:
9546W SPOOL FILES:n SPOOL MODELS:n TOTAL CYLINDERS OF SPOOL MODELS:n
_beta log|z also creates an event (see "Standard events" in _beta log|z Administrator Guide).
The warning threshold is defined via the LST parameter BQL_SPOOLCHECK_MODEL (Allowed:1..9 Default:1).
The check is carried when the STC is started and when a new spool file is allocated.
Support of IPv6 addresses has been added to all functions of the BSA TCP/IP server and the BSA Service Manager.
IPv6 support has also been added to the BSA service routines for the TCP/IP communication in order to enable Beta V7 products to use IPv6.
The changes that have been implemented ensure downward compatibility with IPv4.
Note: IPv6 support has not been added to OCF TCP/IP communication (BSA X-System Router) and the BSA Communication Integrator (BSA CI).
The optional parameter <resolve> has been added to the PORT LST parameter of the TCP/IP server. The <resolve> parameter controls which numeric IP addresses are used for the bind following the resolution of a symbolic IP address.
Syntax
Bnn_TCPIP_PORT[_app] = port,ipa[<resolve>],tcpname[,[clnt],[mssid],[rssid],[keepalive]]
Parameter |
Description |
Opt./Req. |
---|---|---|
port |
Listening port (max. 5 digits) |
required |
ipa[<resolve>] |
Bind address (numeric or symbolic) Use the following notations if you want to specify an all-zeros address to bind to all available interfaces: 0.0.0.0 All available IPv4 addresses; accepts only connections via IPv4 protocol. IPA_ANY4 Same as 0.0.0.0 :: All available IPv4 and IPv6 addresses; accepts connections via IPv4 and IPv6 protocol. IPA_ANY6 Same as :: Symbolic addresses (max. 255 characters) are resolved to numeric addresses (IPv6 and/or IPv4) via DNS. The resolution sequence is determined by the DNS server. By default, IPv6 addresses have precedence over IPv4 addresses. You can use the <resolve> parameter to control DNS resolution if ipa is a symbolic address: ipa The TCP/IP server uses all addresses from DNS resolution and binds to the first reachable IPv6 address and to the first reachable IPv4 address. This is the default, which is adequate in most situations. ipa<IPV6> The TCP/IP server uses all IPv6 addresses from DNS resolution and binds to the first reachable address. ipa<IPV4> The TCP/IP server uses all IPv4 addresses from DNS resolution and binds to the first reachable address. ipa<IPV6:ALL> The TCP/IP server uses all IPv6 addresses from DNS resolution and binds to all reachable addresses. ipa<IPV4:ALL> The TCP/IP server uses all IPv4 addresses from DNS resolution and binds to all reachable addresses. ipa<ALL> The TCP/IP server uses all IPv6 and IPv4 addresses from DNS resolution and binds to all reachable addresses. The <resolve> parameter has no effect if ipa is a numeric address. |
required |
tcpname |
Name of the TCP/IP started task (TCP/IP stack) on the z/OS system (max. 8 characters) |
required |
other parameters |
See the description of the PORT LST parameter in "LST parameters for the BSA TCP/IP server" in BSA Installation and System Guide |
optional |
DNS resolves TEST03.ZS.DE.EU.BETA.ADS to the following three addresses:
If the following parameter is coded in the active LST member:
B93_TCPIP_PORT_BWE = 64001,TEST03.ZS.DE.EU.BETA.ADS<IPV4>,TCPIP
The BSA TCP/IP server binds to...
...if this is the first reachable IPv4 address. The BSA TCP/IP server cannot be reached at the other two addresses.
If the following parameter is coded in the active LST member:
B93_TCPIP_PORT_BWE = 64001,TEST03.ZS.DE.EU.BETA.ADS,TCPIP
The BSA TCP/IP server binds to:
Code the following parameter in the active LST member if you want the BSA TCP/IP server to be reachable at all addresses:
B93_TCPIP_PORT_BWE = 64001,TEST03.ZS.DE.EU.BETA.ADS<ALL>,TCPIP
New functions have been added to the BSA Service Manager option 4.2.2 (TCP/IP connectivity) with respect to IPv6 support.
For example, you can use the BSA Service Manager to check the resolution of symbolic IP addresses:
PEB4TCPD ------------------------------------------------------- Row 1 of 4 Command ===> ________________________________________________ Scroll ===> PAGE TCP/IP Application Control - Resolve DNS Subsys-ID - B93W Sysname - BETA Product STC : RABBIT IP-Address : ----------------------------------------------------------------------------- BLN-REJA2DSKW7 ----------------------------------------------------------------------------- Task Resolved IP-Address Styp HOSTID(V4) TCPIP 2001:8DB:A:75:8F65:5B26:9720:4AB1 1C13 10.56.83.100 TCPIP 10.56.75.7 1002 10.56.83.100 TCPDEV 2001:8DB:A:75:8F65:5B26:9720:4AB1 1C13 10.56.83.115 TCPDEV 10.56.75.7 1002 10.56.83.115 ******************************** BOTTOM OF DATA ******************************** |
The BSA Service Manager can also be used to display TLS status information on addresses/ports:
PEB4TCPS ------------------------------------------------------- Row 1 of 3 Command ===> ________________________________________________ Scroll ===> PAGE TCP/IP Application Control - Display Ports/Users Subsys-ID - B93W Sysname - BETA S Pr Port Port TLS Status Resolved IP-Address Type Stack Status B93 BWE 49317 TCPIP TLS#NOPOL 10.56.83.100 B93 BWE 49317 TCPIP TLS#NOPOL 10.56.83.101 B93 BWE 49327 TCPIP ACTIVE 10.56.83.102 ******************************** BOTTOM OF DATA ******************************** |
For a complete description, see the BSA Service Manager Manual.
For a list of earlier changes, see BSA V6R1 Installation and System Guide.