Re: BPCS and using the Sys Req Attn key.

First, Sys-Req and Attn are two different things.  On the old crappy 
twinax terminals they were printed on the same key.  Simply hitting that 
key was attention.  Shift and that key was Sys-Req.  The difference being 
important to note because there are things like SETATNPGM.  If I remember 
a way to limit SysReq, I'll let you know.


Rob Berendt
-- 
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   [email protected]
To:     BPCS ERP System <bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]>
Date:   12/05/2016 02:17 PM
Subject:        Re: [BPCS-L] BPCS and using the Sys Req Attn key.
Sent by:        "BPCS-L" <bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]>



Rob,

QLMTDEVSSN is set to 0, do not limit.
QAUTOCFG is set to 1, ON, but they plan to turn that off to 
better/manually manage devices soon.

Couple things...
Thing 1 - even though they bought-the-source-code, they have some sort of 
limit as to
how many bpcs users can be on at the same time, which. . .  seems well, at 

least weird.
I think the limit is 250, and was decided i think in the past when they 
upgraded to a different/newer box.

Thing 2 - a bunch of this software uses data areas, assigned for this 
process or that, that
are comprised of a prefix (usually 2 character), followed by the first 8 
characters of the wsid.
This has given us issues in the past with autocfg'd devices as the data 
area names need to be unique.


I too feel that Sys Req Attn is antiquated and should be deprecated, at 
least then we could be 'more' sure of unique device ids.

Thing 3 - 'Where' things get directed to print around here are driven by 
wsid, NOT user id,
(i know, wouldn't be my first choice), 

Anyway in light of the 250 user bpcs limit -and- printer routings based on 

wsid devices i understand devices need to be controlled.

I just don't like Sys Req Attn!!!!!

John

ps.
I'm not the admin here, just a programmer.

Multiple http, file transfer,shared folder...   i have no idea but afaik 
most of any http
stuff here is only BCD Websmart stuff which i have nothing to do with.


<snip>
Is this a shop which follows some weird auditor requirement that system 
value QLMTDEVSSN be turned on?  Therefore inhibiting them from using 
multiple sessions the "right" way and requiring the Sys-Req-"1. Display 
sign on for secondary job" option?  I would fight that and maybe your 
issue would go away.

IMNSHO QLMTDEVSSN should have been deprecated after the first multiple 
session twinax terminal came out.  Are there system values which limit 
someone from multiple http sessions?  Multiple File Transfer sessions? 
Having more than one shared folder open?


Rob Berendt
-- 
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   [email protected]
To:     "BPCS ERP System (bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected])" <bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]>
Date:   12/05/2016 12:02 PM
Subject:        [BPCS-L] BPCS and using the Sys Req Attn key.
Sent by:        "BPCS-L" <bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]>



I'm somewhat new to bpcs but it seems as though users who have acess to 
the SysReqAttn key keep getting themselves in trouble and locking, for 
example, orders up by going at the same ones from 2 sessions with the same 



workstation id.

Our bpcs versiion was outright purchased, source and all in the 90s, hence 



no updates etc (except for what we write).

It seems like it would be good practice to lock users out of using the Sys 



Req Attn key for getting another session.

I'm wondering if anyone else out there has come to this conclusion?

John
</snip>
<br />
The information in this email is confidential and may be legally 
privileged.
It is intended solely for the addressee. Access to this email by anyone 
else is
unauthorized. If you are not the intended recipient, any disclosure, 
copying,
distribution or any action taken or omitted to be taken in reliance on it, 
is
prohibited and may be unlawful.
-- 
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.



-- 
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.