× 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.


  • Subject: Re: EXTREME EMERGENCY! - FSIOP DEAD AFTER V4R5 UPGRADE
  • From: MacWheel99@xxxxxxx
  • Date: Sun, 22 Oct 2000 15:26:22 EDT

Your choices depend on whose decision it was to upgrade & whether they had 
fair notice of what later versions of OS/400 do not support.  I have been 
telling my management now for ONE YEAR about stuff that a later release will 
not support that we depend on in daily operations & that we need to reach a 
consensus on what to do about it & the replies range from dead silence to 
people who do not like the application who are happy that it will die.  I 
suspect the people who will be most affected are so drowned in day to day 
operations & my other memos that the situation does not penetrate their 
conscious thoughts what to do about this.

Thus if you were TOLD to install this OS/400 version by some manager who KNEW 
what it would not support, although perhaps they had forgotten the nuance or 
implication ... you just tell everyone that manager decided to pull that 
plug, it was not an IT decision, you were just following orders.  However, it 
is only fair to get that manager on the phone & ask for confirmation that you 
not going to be running that application any more, as opposed to trying to 
restore from before the upgrade, and postpone the upgrade to a later weekend 
after full confirmation that no one needs LAN access any more via OS/2.

In other words, if you went back to an earlier version, restoring your backup 
of OS/400 etc. prior to the upgrade, so as to support what was lost, this 
might be in violation of orders for you to upgrade.

Let's suppose you were told to do this upgrade by someone who did not know 
about what support you would lose.  There will be some finger pointing as to 
why that person did not know that.  You should have a hardware support outfit 
that knows what you are using the AS/400 for & they should know what is lost 
that is relevant to your company with each release & they should tell your 
management about such problems in advance.  

Ask if in fact management was told by your hardware vendor what your vendor 
has a fiduciary responsibility to say, especially if they have an updated 
version of your sizing questionairre ... and if they do not - ask why not.  
If management was told what your hardware vendor should have told them, then 
management should have known that this upgrade would kill some applications 
that the company had been using, and this should have been no surprise to 
you.  They should have told you that the plug was being pulled on this stuff 
deliberately.

If you are not doing business with any such competent vendor, and if 
management had no advance warning of this scenario, then you need to restore 
to backup prior to the upgrade, explain situation to management, and update 
your resume'.

You do have a recent SAVE 21 from before the upgrade I hope?

> Subj:  EXTREME EMERGENCY! - FSIOP DEAD AFTER V4R5 UPGRADE
>  Date:    10/22/2000 12:29:31 PM Central Daylight Time
>  From:    Patrick.Archibald@HOMETELCO.COM                  
>            
>  From . . . . HTPLAINF HTPLAINF  Patrick L Archibald                        
  
>            
>  Date . . . . October 22, 2000
>  Time . . . . 12:50:09 PM
>  Subject  . . EXTREME EMERGENCY! - FSIOP DEAD AFTER V4R5 UPGRADE            
  
>            
>  
>  Hi 
>  
>  I screwed up big time!  I upgraded 0S400 to v4r5m0 last night.  I 
>  didn't realize that this release doesn't support the OS/2 version of 
>  the LAN server FSIOP.  (CRTNWSD  TYPE(*LANSERVER))  I've got the 2850 
>  file server IOA. 
>                                    
>  
>  I have backup copies of the data using the SAV DEV(&IFSDEV) 
>  OBJ(('/QLANSRV/NWS/SERVER01/DSK')) method.  This command just backs up 
>  the storage spaces and doesn't allow you to restore files just the 
>  entire space. 
>  What are my choices? 
>  
>  1. Degrade from OS400 V4r5 to v4r4?  What kind of problems will this 
>  cause? 
>  
>  2. Find someone with a similar configuration to mine before I upgraded 
>  and get the files restored? 

>  3. Find another job? 
>  

4. File Chapter 7 Bankrupsy because your company is now out of business.

5. Get a lease on ANOTHER AS/400 box with a smilar configuration before the 
upgrade, to run the applications that cannot afford to be on a current box.

>  
>  Thanx, PLA
>  
>  /
>  / Patrick L Archibald
>  / Home Telephone Company
>  / Moncks Corner SC USA
>  / Patrick.Archibald@HomeTelco.Com
>  / http://HomeTelco.Com/pla/
>  / Voice 803-761-9190
>  / DCS Mobile 803-813-4803
>  / DCS Email 18438134803@blsdcs.net
>  / Fax 803-761-6869
>  /
>  / This mail document was created and sent using 
>  / IBM AS/400 OfficeVision V4R5M0.


Alister William Macintyre 
Computer Data Janitor etc. of BPCS 405 CD Rel-02 on 400 model 170 OS4 V4R3 
(forerunner to IBM e-Server i-Series 400)  @ http://www.cen-elec.com Central 
Industries of Indiana--->Quality manufacturer of wire harnesses and 
electrical sub-assemblies

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.