RE: Cume causes purchase or hardware was: CL Variable being chang ed by called CL program

I was never exactly clear about how/when/what happened with this stuff.  As
I recall, V5R1 (maybe V4R5) upgrade announcement stated the intent to
disable the DOS based PCS interface, but as I recall, it still seemed to
work ok at V5R1.  We haven't gone to V5R2 yet, and since we decided to
eliminate the SAA server, we won't be able to test this again.  There look
to be a few documents in the Knowledge base that point toward issues with
user defined mode descriptions....  

Still, I think the new scanners were probably the best solution to you
problem....

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Fisher, Don [mailto:Dfisher@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, June 02, 2004 8:58 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Cume causes purchase or hardware was: CL Variable being
chang ed by called CL program


That is possible, but if that were so, why did the scanners work after we
upgraded to V5R2 and cease working only after applying the cume?

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
I'd bet you had a Novell SAA server that was used by the emulation software
in your scanners.  This was a common requirement for older emulation
software, and as I recall, it was disabled with V5, along with support for
many of the DOS based APPC PC Support packages.  <clip>
--
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.