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

I certainly understand needing quick action to get the scanners up.
I hope someone out there knows what changed in a V5R2 (?) cume
that would affect sna communications. Did Symbol have a
server pgm running on the AS400? Any security audit jrn entries related to
this?
I've seen release upgrades cause non-IBM
hardware to drop when the hardware is not up to IBM's spec. Did the
vendor give any indication they knew what was going on?
jim
----- Original Message ----- 
From: "Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, June 02, 2004 8:04 AM
Subject: RE: Cume causes purchase or hardware was: CL Variable being chang
ed by called CL program


> All we know is we applied the cume over the weekend and when the
> distribution center started work Monday, the Symbol scanners were not
> communicating with the system.  IBM was unhelpful in solving the problem
and
> the scanners were so old as to preclude hardware support from the vendor.
> There might have been some "selling us something" going on, but we had to
> move quickly and managed to get rid of some really old hardware in the
> process that was likely causing problems anyway.
>
> Donald R. Fisher, III
> Project Manager
> Roomstore Furniture Company
> (804) 784-7600 extension 2124
> DFisher@xxxxxxxxxxxxx
>
> <clip>
> Do you have any documentation or confirmation from IBM this is true? or
was
> it the vendor "selling you something"?
> The only way I can imagine a ptf changing something like this is if the
> vendor was doing something on an unsupported interface
> (and i can't imagine what that would be.
> jim
> <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.
>
>