Don't you have to use CHGS36 command to add a two digit code for each
workstation?

Jack

On Tue, Aug 11, 2015 at 2:26 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

The table may be full? Just a thought.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.


On 8/11/2015 2:21 PM, T. Adair wrote:

Here's an interesting situation - we use QEXCVTDV to retrieve the old S/36
workstation ID in a CL program. This has been working fine for a few
years.
We've now defined a few new workstations (sessions) at a new location, and
they are working great except QEXCVTDV is returning "0" (zero - Unknown).
The CL program is still working fine for everyone else - just not for the
new workstations.

I'm wondering if it has something to do with the naming convention. The
new
workstation sessions all start with RWPC. I'm not at the new remote site,
or else I could define a new session (call it "FRED" or something) and see
if that makes a difference.

I will probably have to change the CL program logic to used some other
method (which is certainly feasible), but this issue really has me
curious.
We're currently on 7.1. And yes, I have searched the archives, and
Googled
it. No soap.

As always, any thoughts are appreciated.

TIA.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].