RE: AS/400 USER PROFILE -- SYSTEM21

Jeff/All:

Do not forget that role menus and the primary databases that control
Explorer and the available blueberries can sit in a Network location.  You
do not have to install custom menus on hundreds of PCs.  Many System/21
customers use Explorer in this way.

Networking your role menus and databases allows tighter control of Explorer
and @ctive Modeler process flows.  I would be glad to discuss this with you
offline.

Thanks,

Bob Keeley
Account Manager
JBA International, Inc.
A unit of Geac Enterprise Solutions
Cell: 440-227-0723
Office: 248-380-6900, x. 4411
Home Office: 440-209-9992
e-mail: Robert.Keeley@Geac.com


-----Original Message-----
From: Jeff_Klipa/Harvard@harvardind.com
[mailto:Jeff_Klipa/Harvard@harvardind.com]
Sent: Tuesday, August 14, 2001 1:26 PM
To: JBAUSERS-L@midrange.com
Subject: RE: AS/400 USER PROFILE


Well said, Fred...!!!

So let me see if I've got this straight...

If you're strictly using the GUI Blueberries you can :
Change initial program   : jbasmg.ini = *NONE
               : AS/400 profile = CWSINITIAL

If you need to use both GUI Blueberries and Green Screen then CWSINITIAL
cannot
be your INLPGM on the OS/400 profile...
I'm going to assume that for all intents and purposes that a Server Session
is
going to be equivalent to a Green Screen in this discussion...

That would never work for us - we've got too many custom menus that require
users to use Server Sessions...
The original paradigm during our implementation was to use strictly
Blueberries
but that doesn't lend itself well to customization...
I don't feel like keeping a bunch of custom .RMU roles updated on several
hundred PCs...

Good discussion topics...

Thanks...








> A note about "LIMIT CAPABILITIES = *YES"...  You cannot use this if you
are
> using the GUI Explorer package...

Yes you can, sometimes!!

All of the users at one of my clients use JBA Explorer and none of them have
access to the green on black screens.  This was done because when JBA was
installed it was decided that as this was a new system it had to look
different to the old system.

By default the initial program in jbasmg.ini on each users PC is set to
CWSINITIAL.  JBA Explorer simply 'screen scrapes' the AS/400 screens and
when the user signs on, Explorer places this program name in the initial
program field on the AS/400 sign on screen and uses this instead of the
initial program set up in the user profile.  This needs LMTCPB(*NO).

If the user will only use JBA Explorer you set LMTCPB(*YES) and set the
initial program in the user profile to CWSINITIAL.  Then, on the users PC,
change the jbasmg.ini file to set the initial program to *NONE.  When the
user signs on the default initial program on the user profile is used.

Therefore if the user has access only to JBA Explorer or only to green
screens then you can set LMTCPB(*YES).  If they switch between the two then
they must have LMTCPB(*NO).

I do not have a JBA Explorer set up in front of me as I prefer green on
black and I may have got some of the file names wrong but if anyone is
interested I can get the details for them.

--
Fred Mitchell
Concise Consulting Ltd.
Newcastle upon Tyne, England
mailto:fred@ccl400.com
http://www.ccl400.com



+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---