× 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. MIDRANGE-L
  3. April 2016

Re: Considerations for changing QPWDLVL from 0 or 1 to 2

Yeah, I was thinking overlaying would be a problem...

If scanners are your concern...do you really need the Program & Menu lines
there in the first place?

Would removing the text and protect/non-displaying those fields solve your
concerns?

Charles

On Wed, Apr 27, 2016 at 2:10 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

I think overlaying is going to be a serious issue.

I dropped password down to 6 characters to allow me to use 4 characters
for my dummy. This allows me to practice overlaying without having the
start right at the start of the other field. With only 2 characters it
would have been tough.
Then I moved my dummy down and had it start 2 characters before the entry
field for program.
This seemed to clobber the field start attribute for PROGRAM and made it
unusable.

A 06 17'User . . . . . .
A USERID 10 B 06 53
A 01 07 17'Password . . . .
A 01 PASSWRD 6 I 07 53
A DSPATR(ND)
A DUMMY 4 I 08 51DSPATR(PR ND)
A 08 17'Program/procedure
A PROGRAM 10 B 08 53CHECK(LC)

I ended up with
User . . . . . . . . . . . . . . __________
Password . . . . . . . . . . . .
Program/procedure . . . . . . . .
Menu . . . . . . . . . . . . . . __________
Current library . . . . . . . . . __________

And I could not enter anything for Program. I think that was technically
because the field start attribute was overlaid.


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: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/27/2016 01:57 PM
Subject: Re: Considerations for changing QPWDLVL from 0 or 1 to 2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Now the next check comes down to what happens if the fields are overlaid?
If I have a 128 byte character field starting in row 7 column 53 that
would go down a row or so.
The protected, non display dummy field shouldn't be a problem overlaying
it with this, right?
Program/procedure . . . . . . . . __________
Menu . . . . . . . . . . . . . . __________
Current library . . . . . . . . . __________

What may look only odd and annoying to those with a 'real' 5250 screen
might take those with a scanner and but a quadrant of the screen plumb
over the edge.

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: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/27/2016 01:52 PM
Subject: Re: Considerations for changing QPWDLVL from 0 or 1 to 2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Protected, Non display worked fine!

A USERID 10 B 06 53
A 01 07 17'Password ...'
A 01 PASSWRD 8 I 07 53
A DSPATR(ND)
A DUMMY 2 I 07 62DSPATR(PR ND)


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: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/27/2016 01:40 PM
Subject: Re: Considerations for changing QPWDLVL from 0 or 1 to 2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



and/or maybe a non-display input field...

Charles

On Wed, Apr 27, 2016 at 1:37 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Rob,

Think you'd have to have DUMMY be a protected input field rather than a
hidden one.

Charles

On Wed, Apr 27, 2016 at 1:28 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

I tried it with, and without, the 2 byte hidden field after dropping
the
password from 10 characters down to 8.
A 01 07 17'Password ...'
A 01 PASSWRD 8 I 07 53
A DSPATR(ND)
A* DUMMY 2 H

The buffer was off by 2 characters either way.

For the following:
User . . . . . .
Password . . . .
Program/procedure
Menu . . . . . .

I would enter in:
ROB

*none
main


But I would get back
ROB

one ma
in
CPF1133 Value one ma is not a valid name.


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: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/27/2016 01:02 PM
Subject: Re: Considerations for changing QPWDLVL from 0 or 1 to
2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Well, gee, we have this sandbox lpar for a reason, eh?
And as long as I only modify the signon screen for qinter and not qctl
I
can always back it out from my hmc console session (remotely even).

So, before I change any system values I could break up the 10 character
password screen into 8 & 2.


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: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/27/2016 12:58 PM
Subject: Re: Considerations for changing QPWDLVL from 0 or 1 to
2
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On Wed, Apr 27, 2016 at 10:27 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Is it possible to modify the signon screen to just make the password
field
our chosen maximum instead of the full 128 characters?



​Rob,

My first thought is that you can't do that...

"Field names and buffer lengths should not be changed."




https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzarl/rzarlchgdsp.htm?lang=en






My second thought is maybe you can...



https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzarl/rzarlchgdspfl.htm?lang=en






Say you were to change the length of PASSWRD to 20, you'd have to add a
dummy hidden input field of length 108 between PASSWRD and PROGRAM.

That would keep the total input/output buffer length unchanged.

I don't have time to try it...

But if you do, I'd be interested in the results. :)

Charles
​
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.