|
midrange.com
The "supported" upgrade is 5.1 on the 600 and a OPT#21 save and restore...
only thing left behind are spoolfiles...
_____________________
Kirk Goins
Systems Engineer, Manage Inc.
IBM Certified iSeries Solutions Expert
IBM Certified iSeries e-Business Infrastructure
IBM Certified Designing IBM e-business Solutions
Office 503-353-1721 x106 Cell 503-577-9519
kirkg@manageinc.com www.manageinc.com
rob@dekko.com
Sent by: midrange-l-bounces@midrange.com
01/13/2003 12:27 PM
Please respond to Midrange Systems Technical Discussion
To: Midrange Systems Technical Discussion <midrange-l@midrange.com>
cc:
Subject: Re: 24x80 size issue
You need various IFS folders where is this data is stored.
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
"Anthony Hardy" <mis@jdcc.edu>
Sent by: midrange-l-bounces@midrange.com
01/13/2003 02:04 PM
Please respond to Midrange Systems Technical Discussion
To: "Midrange Systems Technical Discussion"
<midrange-l@midrange.com>
cc:
Fax to:
Subject: Re: 24x80 size issue
Copied user libraries and did backup of sec data and restored to new
machine. I can look on the old machine for settings if anybody can point
in
the right direction.
Anthony Hardy
Director of MIS
Jefferson Davis Community College
----- Original Message -----
From: <rob@dekko.com>
To: "Midrange Systems Technical Discussion" <midrange-l@midrange.com>
Sent: Monday, January 13, 2003 12:21 PM
Subject: Re: 24x80 size issue
> How was the upgrade done? Was the actual 600 physically upgraded to a
> 170? Or did you copy a few libraries, etc over to a new 170?
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
> "Anthony Hardy" <mis@jdcc.edu>
> Sent by: midrange-l-bounces@midrange.com
> 01/13/2003 12:44 PM
> Please respond to Midrange Systems Technical Discussion
>
> To: <midrange-l@midrange.com>
> cc:
> Fax to:
> Subject: 24x80 size issue
>
>
> Quick question:
>
> Had a model 600 - upgraded to a 170, all sysvals the same, OS/400 stayed
> at 5r1.
>
> I have some thin clients that worked fine pre-upgrade, but now, post
> upgrade, I get an error concerning the "clients" ability to show
> fields/data outside of the 24x80 workspace. Extended display error. The
> third party vendor tells me they haven't seen this in a LONG time (not
> since some VERY old terminals were in use) and that all newer terminals
> should be able to handle the way things are NOW.
>
> Our existing dumb terminals (3477FGs over twin-ax) handle everything
just
> fine, as do our CE sessions. I'm stumped b/c the thin clients DID work
> just fine before the change in AS400s and I am too much of a novice to
be
> able to tell what is happening. I have manually created devices to see
if
> that is the problem - no. Autocreate - no.
>
>
> Secondly . . and I'm certain this is tied into the same issue, deals
with
> printing. I setup a session on the thin clients for printing, manually
> create the printer (with model type, etc) and everything was working
> great. We changed systems and now I get what looks like about four
lines
> of ascii column and row "headers" boxing in the correct printout. The
> thin client setup did not change . .and I am stumped.
>
> Any ideas?
>
> Thanks!
>
> Anthony Hardy
> Director of MIS
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.
