Paul, The elegant and user-friendly way to do this sort of thing is to exploit the use of the PORT statement BIND parameter in conjunction with VIPAs. This way you can offer an REXEC service on port number 512 for either TSO or USS and distinguish the two by IP address which, of course, can be extended to a separate name fore each service with the cooperation of the name service.
Having written that, I thought I'd "go the extra mile (1 3/5 kilometres)" and provide an example. Wouldn't you know it, the CS IP authors have beaten me to it - in section 2.18.5, "Configuring TSO and z/OS UNIX Remote Execution servers to use the same port", of the z/OS Communications Server IP Configuration Guide? I'd be inclined to go the extra yard (appox. 1 metre) and use a VIPA for both services instead on just the one - but then I'm a perfectionist. <g> Oh, and why they don't mention being really helpful and propose names such as rexec.tso.abccorp.com and rexec.unix.abccorp.com I don't know. Chris Mason ----- Original Message ----- From: "Paul Gilmartin" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Monday, 03 April, 2006 4:25 PM Subject: Re: REXEC and TSO <snip> > o Prevail on your site to run the TSO-flavor REXECD on a different > port. Direct your client REXEC commands to that port. </snip> ---------------------------------------------------------------------- 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
