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


  1.  Home
  2. SYSTEM21
  3. June 2002

SYS21 - RE: SYS21 - SYS21 - System21 Explorer

Yeah, there is a system value QAUTOVRT that allows you to automatically create
Virtual Devices when they connect...
You can only specify a threshold number beyond which it will not create any more
virtual devices automatically...
It gives you no control over the name it assigns...

QPADEVxxxx
Q=IBM proprietary letter - they own the letter Q don't you know...!!!
PA=Passthrough I believe is where this comes from (I could be mistaken)...
DEV=Device...
xxxx=A 4 character sequence for uniqueness...

You'll note also that it doesn't matter if you're using the blueberries in
Explorer or a Server Session you still get a QPADEVxxxx terminal ID assigned...
CWSINITIAL is the program that is called if you use the GUI blueberries...
The 5250 Server Session will call whatever Initial program to call  . . . .
INLPGM you define in their use profile...

So depending on which approach you take there may be some control to be taken in
the INLPGM or CWSINITIAL...

Good luck...

PS - If you can identify or hardcode the workstation name you can force it to a
specific subsystem...

   Modify the necessary workstation entries. For each workstation that you want
     to move to the new subsystem, issue the following commands:
      ADDWSE SBSD(QINTER)              +
             DEVNAME(xxxx*) AT(*ENTER)
      ADDWSE SBSD(new-subsystem)       +
             DEVNAME((xxxx*) AT(*SIGNON)


     where xxxx is the workstation name and new-subsystem is the new subsystem's
     name.


     The workstation name can be generic so QPADEV* will move all devices
     created thusly to whatever subsystem you desire...

 *SIGNON
     The work stations are allocated when the subsystem is started if
     the work station is not already in use (signed on) in another
     subsystem.  A sign-on prompt is displayed at each work station
     associated with this work entry.  If a work station becomes
     allocated to a different subsystem, interactive jobs associated
     with the work station are allowed to enter this subsystem
     through the Transfer Job (TFRJOB) command.

 *ENTER
     The work stations associated with this work entry are not
     allocated when the subsystem is started.  However, the
     interactive jobs associated with the work stations are allowed
     to enter this subsystem through the Transfer Job (TFRJOB)
     command.









"Kincer, Alan" <akincer@kiusa.com> on 06/21/2002 12:15:02 PM

Please respond to jbausers-l@midrange.com



  To:          "'jbausers-l@midrange.com'"
               <jbausers-l@midrange.com>

  cc:          (bcc: Jeff Klipa/Harvard)



  Subject      RE: SYS21 -  SYS21 - System21 Explorer
  :







This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]


Don't know if this is directly applicable to the original problem but there
is a note on geacUser's info on display emulation.

Currently none of our Client Access machines have workstation IDs assigned
to them. Apparently they pick up some lengthy "Qxxxxxxx" ID from the 400 and
seem not to have any problems as such.

At a prior job we did give all the CA workstations names and it was a little
more problematic. There sessions locked up frequently and if this happened
someone in Louisville (half a state away) or someone with CL authority had
to kill the job in QINTER either *CTRLD or *IMMED before the user could
reconnect.

Although all the users where I'm at now are local with their 400 no one ever
has a lock up. I think the locking issue may have been due to the remote 400
connection but naming the workstations just made things more frustrating
when trying to reconnect.

Anyway just a thought.

Alan



-----Original Message-----
From: Geac User [mailto:geacuser@yahoo.com]
Sent: Friday, June 21, 2002 12:03 PM
To: jbausers-l@midrange.com
Subject: RE: SYS21 - SYS21 - System21 Explorer


Here is the text of that article.
I don't think this helps you though.  This is for
Client Access Express.  I'm not sure you can control
the name assigned to the Server Session when it
connects.  You should be able to control the Subsystem
it opens in though.  I'm sure someone at ANSWERLINK
has the info you need on this topic.  There is
probably an .ini file setting somewhere.

I'm wondering why you would want your users to run in
something other than QINTER which is the default?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Does PC5250 display emulation let me assign a unique
workstation device ID, or does TN5250 assign it
randomly when I connect to an AS/400?
by Carole Miner

Q: Does PC5250 display emulation let me assign a
unique
workstation device ID, or does TN5250 assign it
randomly when I connect to an AS/400?

A:You can select your workstation device ID when using
either Client Access for Windows 95/NT or Client
Access Express PC5250 emulation. However, many
additional PC5250 capabilities have been available for
Client Access Express since January 2000 via Service
Pack SF60698 or later.

Many emulation programs don't handle 5250 workstation
IDs over TCP/IP very well, and users and
administrators want more control over how workstation
IDs are assigned and maintained.

The Express client has improved this area so that you
can select your workstation ID, have multiple 5250
sessions, and maintain everything in one workstation
(.WS) profile.

A .WS profile is where information about a 5250
session is stored. AS/400 administrators can choose to
maintain only one .WS profile on an AS/400 and have it
shared by all PC5250 sessions, thus enabling
standardization of settings. Alternatively, users can
save their .WS profiles on their PCs and change them
to suit their preferences.

IBM has added a new parameter for setting up the
workstation ID name. The format of this
parameter is :

Workstation
ID=[+][%](Workstation_Name/&COMPN/&USERN)[*][=]
 + indicates to truncate the workstation ID from the
end if it's longer than 10 characters
 % adds P (Printer) or S (diSplay) to the front of the
workstation's name
 Workstation_Name is the "hardcode device name" (e.g.,
"WS1")
 COMPN is the Computer name (this is the name
identified in the Windows Network Identification area)
 USERN is the Windows User name
 * means add a suffix (e.g., A, B, C) to the
workstation ID
 = means auto-increment the workstation ID if
additional sessions are started
(increments go from 1 to 9, then A-Z)
By establishing guidelines for naming the workstation
ID for display and printer sessions,
AS/400 operators and administrators can more easily
determine what's attached to their
AS/400 at any time.

Article Information
Article ID: 8981
Pub: iSeries NEWS
Dept: FAQ
Date: July 01, 2000


I look forward to hearing how this one works out.


--- "Wojcik, Lorri" <LWojcik@pts-tools.com> wrote:
> It can be done.  The Tech tip in the July 2000 issue
> of News/400 magazine on
> page 121 tells how that can be done.  I think you
> can search their website
> if you don't get this publication.
> www.iseriesnetwork.com
>
>
> Lorri Wojcik
> AS/400 Administrator
> Production Tool Supply
>
>  -----Original Message-----
> From:   Jerram, Stephen
> [mailto:Stephen.Jerram@rexam.com]
> Sent:   Friday, June 21, 2002 8:02 AM
> To:     jbausers-l@midrange.com
> Subject:     SYS21 -  SYS21 - System21 Explorer
>
> We are currently looking at implementing Explorer
> across our 6 sites but we
> are having trouble
> making sure that the interactive jobs go into the
> right sub system.
>
> Is there anyway of giving an Explorer session a
> device name that is not
> QPADEVxxxxxx???
>
> Also can the device name be appended with a variable
> character
> eg my device is call TERM and when i sign on the
> first session is TERM1 then
> TERM2 etc
>
> any help would be appreciated
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L)
> mailing list
> To post a message email: JBAUSERS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
> or email: JBAUSERS-L-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/jbausers-l.
>
>
>
>
**************************************************************************
> This communication (including any attachments)
> contains information which
> is confidential and may also be privileged.  It is
> for the exclusive use
> of the intended recipient(s).  If you are not the
> intended recipient(s),
> please note that any distribution, copying or use of
> this communication or
> the information in it is strictly prohibited. If you
> have received this
> communication in error, please notify the sender
> immediately and then
> destroy any copies of it.
>
> Any views expressed in this communication are those
> of the individual
> sender,
> except where the sender specifically states them to
> be the views of the
> company.
>
**************************************************************************
>
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L)
> mailing list
> To post a message email: JBAUSERS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
> or email: JBAUSERS-L-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/jbausers-l.
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L)
> mailing list
> To post a message email: JBAUSERS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
> or email: JBAUSERS-L-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/jbausers-l.
>


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-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-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.