|
We have had the same problem. The older Client Access software using TCP/IP did not permit you to define your own device name. We had gone with Wall Data's Rumba Product. This allowed us to define our own device names (8 positions or less). Now we are upgrading to i-series 400 and going with the new CA/400 that permits you to define your own device name using TCP/IP. This works well.
It appears that BPCS may have followed the old S/38 convention of device name size that was 8 positions. When used with the default device naming (i.e., QPADEVxxxx) BPCS truncates the right 2 positions of the device name. Unfortunately these positions are the unique identifiers for the device. In BPCS the device controls the outq, jobd, copies, etc.
Unfortunately the only was I have found to handle it is to get emulation software that permits you to reduce the size of the device name to 8 positions so BPCS can operate within its parameters.
Gregg E Savoy
Director Information Technology
Troy Corporation
-----Original Message-----
From: qin_huang@cn.schindler.com [mailto:qin_huang@cn.schindler.com]
Sent: Friday, December 29, 2000 3:19 AM
To: BPCS-L@midrange.com
Subject: how to change the device name for SNA client..
Dear all,
We have BPCS 4.0.5CD, users use SNA client( running on Win95 platform )
with SNA 4.0 server( running on NT server ) to connect to as/400 and using
BPCS. Each time when they logon the terminal will automatically have an
assigned Device name which looks all like this:
QPADEV00XX
However some BPCS transaction program can't work properly if there is more
than 1 workstation have the first 8 character the same in the device name.
So, How to change this to a shorter one?
Thanks in anticipation and best regards,
Huang Qin
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.