Depending on the design of the software and the number of PC routines that you need/want, the approach of one System-LX to connect the client address to the server so that the client can invoke the non-system LX routines is still a valid option if the number and complexity of the non-system LX warrants it. The System-LX could perform SAF authority checking to determine if the client is permitted to 'connect' to the server as well as actually executing the ATSETs and ETCONs.
This technique is especially handy if the existence of one or more of the non-system LX routines can depend on parameter statements/options for the software. Lumping it all together in one large System-LX might not be the best option here. Rob Scott www.rs.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
