ZCC server overview
ZCC server runs a process that identifies a connection request on a specific port. ZCC server can be started manually, or during an IPL, by running a customized procedure. A sample procedure, HFISRV1, is supplied in the sample library hlq.SHFISAM1.
Multiple servers might be simultaneously run, provided different port numbers are used for each server.
For participating products that use the ZCC server, the server negotiates SSL-encrypted communications if configured to do so, then verifies the client user ID, password, or passphrase. If valid, the server creates a new process for that user.
The ZCC server consists of a main program module, HFISRV, and supporting message and API-related modules.
HFISRV requires
a parameter string 'port family trace' where:
- port
- Describes the port number that is used to bind and accept incoming connections.
- family
- The addressing family to bind to. For example,
AF_INET, orAF_INET6. - trace
- N, T, D, U, or omitted. This parameter specifies the level of tracing to be performed by the server, and is intended only for diagnostic purposes. N is for no tracing, while T or D produce HFITRACE, or STDOUT, outputs of undocumented messages that show flow and processing details for diagnostic purposes. U produces trace entries showing user connections to participating HCL Z products.