Network environment variables in DataStage
These environment variables are concerned with the operation of DataStage® parallel jobs over a network.
APT_IO_MAXIMUM_OUTSTANDING environment variable in DataStage
Set the APT_IO_MAXIMUM_OUTSTANDING environment variable tp specify the amount of memory, in bytes, allocated to an DataStage job on every physical node for network communications.
The default value is 2097152 (2 MB).
When you are executing many partitions on a single physical node, this number might need to be increased.
APT_IOMGR_CONNECT_ATTEMPTS environment variable in DataStage
Set the APT_IOMGR_CONNECT_ATTEMPTS environment variable to specify the number of attempts for a TCP connect during a connection failure.
Setting APT_IOMGR_CONNECT_ATTEMPTS is necessary only for jobs with a high degree of parallelism in an MPP environment. The default value is two attempts, one retry after an initial failure.
APT_PLAYER_CONNECTION_PORT environment variable in DataStage
Set this environment variable to specify the base port number to use when binding the listener port for setting up TCP/IP connections between players.
APT_PM_CONDUCTOR_HOSTNAME environment variable in DataStage
Set the APT_PM_CONDUCTOR_HOSTNAME environment variable to the network name of the processing node from which you start a job, if it is not included in the configuration file.
Include the network name of the processing node from which you start a job in the configuration file as either a node or a fastname. If the network name is not included in the configuration file, you must set the environment variable APT_PM_CONDUCTOR_HOSTNAME to the name of the node that is starting the DataStage job.
APT_PM_CONDUCTOR_TIMEOUT environment variable in DataStage
Set this environment variable to control how long the section leader waits for a response from the conductor.
APT_PM_NO_TCPIP environment variable in DataStage
Set the APT_PM_NO_TCPIP environment variable to turn off use of UNIX sockets to communicate between player processes at run time.
If the job is being run in an MPP (nonshared memory) environment, do not set this variable, as UNIX sockets are your only communications option.
APT_PM_NODE_TIMEOUT environment variable in DataStage
Set the APT_PM_NODE_TIMEOUT environment variable to control the number of seconds that the conductor waits for a section leader to start and load a score before deciding that something has failed.
The default for starting a section leader process is 30 seconds. The default for loading a score is 120 seconds.
APT_PM_PLAYER_TIMEOUT environment variable in DataStage
Set this environment variable to specify the number of seconds that the proto section leader waits for player processes to respond before stopping.
APT_PM_SHOWRSH environment variable in DataStage
Set the APT_PM_SHOWRSH environment variable to display a trace message for every call to rsh.
APT_PM_STARTUP_PORT environment variable in DataStage
Use this environment variable to specify the port number from which the parallel engine starts looking for TCP/IP ports.
By default, DataStage starts looking at port 10000. If you know that ports in this range are used by another application, set APT_PM_STARTUP_PORT to start at a different level. Check the /etc/services file for reserved ports.
APT_RECVBUFSIZE environment variable in DataStage
Set the APT_RECVBUFSIZE environment variable to specify the per-connection TCP/IP buffer space that is allocated.
The per-connection TCP/IP buffer space might need to be set if any stage within a job has many inter-node communication links. The value is specified in bytes.
- APT_SENDBUFSIZE
- APT_IO_MAXIMUM_OUTSTANDING
Set APT_SENDBUFSIZE or APT_RECVBUFSIZE in preference to APT_IO_MAXIMUM_OUTSTANDING for more efficient use of buffer space.
APT_USE_IPV4 environment variable in DataStage
Set this environment variable to force network class to use only IPv4 protocols.
- If your computer is only IPv4 enabled and IPv6 protocol is unavailable.
- If your computer has IPv4 address mapping defined in /etc/hosts file.