Hello all,

The latest in the saga: Trying to get to the operator's console

The person who set up the AS/400 here (model 250 running version 5.1) is out
until 1/8.  It appears that the operator's console has never been
accessible.  Jim Franz pointed me to an iSeries 101 course online that
includes a section "Configure AS/400 Operations Console".  In the process of
setting up the connection via Client Access Express, there are three
options, dialup connection via modem, LAN attach, or or direct cable
connection.  Using the PC Control Panel to get to Modems, the PC indicates
an AS/400 modem is installed on COM2.  However walking thru the console
configuration steps, I reach a point where the AS/400 software displays a
message indicating a modem needs to be installed.  The second option, the
LAN connection, requires a special CD-ROM that we don't have.  Last option:
I compared the cables going into the AS/400 and the graphic showing how to
cable the 250 model. It looks like we should have been able to use the
direct attach option.  However when I attempt to enable that option when
walking thru the configuration, the direct cable option is displayed
protected as though the connection doesn't exist.

So none of the three options appears to be set up correctly.

If someone on the list is running in the same environment and wouldn't mind
giving me their number offline, I would really appreciate being able to
discuss this for a few minutes.

TIA
Jill Grine
jillg@gtsoftware.com


-----Original Message-----
From: MacWheel99@aol.com [mailto:MacWheel99@aol.com]
Sent: Friday, December 21, 2001 10:30 AM
To: midrange-l@midrange.com
Subject: Re: AS/400 Backup questions (was: Probably very easy, Newbie
question )


If you are not doing standard backup like GO SAVE 21 but some mixture
suggested by other folks on this list, some of the stuff you will need in
your list of steps:

ENDSBS SBS(*ALL) then F4

If in doubt, about all the stuff you need to mess with, an easy way to get
rid of everyone, although it takes you longer, before doing the ENDSBS

PWRDWNSYS F4
make it immediate & make it restart from the panel
this is a bit dangerous if you have not yet found your main system console

CHGMSGQ QSYSOPR F4 & make delivery *BREAK or *NOTIFY
have a discussion here with people advising you which is best
We also muck with SEVERITY setting

Then there are a bunch of SAV* commands (I gave a list in an earlier post)
but there's parameters associated with each, for example

SAVDEV('/QSYSLIB/TAP01/DEVD') OBJ('/') ... and it goes on & on with you have
to fill it out exactly just right

then when you all done
STRSBS SBSD( inside parentheses do QBATCH or QCTL or whatever is right for
your 400)

then put delivery mode on system error messages back the way it was

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)
_______________________________________________
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/cgi-bin/listinfo/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 thread ...


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

This mailing list archive is Copyright 1997-2022 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.