To indicate to the z/OS PowerExchange Listener that the second port is associated with a netport, add a NETPORT statement with the same port number. For example:
You can use the TAPEJCL member as a template. Add a job card with "%N5" appended to it, and any other DDs that you might need for your PowerExchange Listener job.
When the z/OS PowerExchange Listener detects activity on the netport, instead of directly trying to service it, the Listener tries to submit the JCL file that is specified in the fifth positional parameter of the NETPORT statement to the JES internal reader. As the JES reader reads and submits the JCL, it scans every JCL line for %
x
tokens, where
x
is a numeric value from 1 through 8. The JES reader substitutes these tokens with the appropriate values from parameters 6 through 13 in the NETPORT statement.
Do not confuse the %
x
tokens with the %N
x
tokens. The %N
x
tokens are used to generate incremented numeric values of
x
length.
You can then submit the GDGJCL job whenever a request is received through the assigned port for the netport job. This action enables a job to end and another job to begin and process the GDGs on z/OS appropriately.
Stop and restart the PowerExchange Listener on z/OS.
Whenever you access a GDG, point to the z/OS GDG location instead of to the z/OS location.
Informatica uses cookies to enhance your user experience, improve the quality of our website, and deliver advertising and other content tailored to your interests. Some jurisdictions’ privacy laws offer their residents specific privacy rights, which we respect as described in our privacy policy. To exercise rights that you may have related to cookies, including opt-out of sharing information with third parties for advertising purposes, select "More Info" or see this "Do Not Sell or Share My Personal Information" link.