× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Reminds me of the time I was on the phone with support fixing resource names during a CISC to RISC. The Ethernet card had gotten tagged CTL01 and this made OS/400 very mad and the console a tad, well, gone. So I'm in SST re-mapping this stuff and saying. " So then this becomes GEORGE and this card will be FRED and the next one is MARY, and " When the IBM guy finally interrupts me with this incredulous tone of voice: "Um, you're not really giving the resources people names are you?" I relied "Sure, I just love it when the local CEs see these names, what a hoot!" to which he replied "I'm gonna have to find a way to get my name off this call record...." OK I was just kidding but it was a good humor moment for o:dark 30 in the middle of a migration!

 - Larry

rob@xxxxxxxxx wrote:
Thanks Larry. Normally I tweak the resource names via SST before I start any restores. After messing with software packages that may reconfig on a whim, like various fax or EDI packages, I've found it's much easier to doctor the resource names via SST than to find hidden data area's, files, menu options, etc to change all these packages.

Been many years since our first AS/400 and comm was down for a few DAYS because IBM inserted a new comm card and the resource names all got shifted. Now I know what I am doing and that CE got promoted out into the wasteland (management).

Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.