|
I used to work with M36 but never 36E so the rules might be different. With M36 it did not matter if the device was valid for WRKCFGSTS on the 400, it also had to be mapped in the A36 configuration to be valid for 36 & it had to have a valid name inside 36 CNFIGSSP. The M36 mapping made it possible to connect a 400 identification like say DSPLAWLB (Display Station in Lawrenceville operated by Lori Blair) to LB (M36 addresses had to be 2 characters) by linking them to a specific port & cable through logical address. It was not possible to define virtual addresses in the 36 world, but so long as we did not exceed the MAX # of 36 addresses that the hardware could handle (e.g. 64 remote devices in Lawrenceville), the 400 was smart enough to link a virtual 400 address to an unused 36 address, when a user did a transfer & we had automatic configuration running. Do you have OTHER virtual addresses talking to your 36? So my question is ... even though this is a valid defined 400 work station, do you have to have definitions for 36 setup before someone tries to use them? For example, have you tried the CHGS36 command specified by the error message? MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)
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.