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



Seems like that blog is not very well indexed on google. I spent 2 hours
googling QDSPSIGNINF and didnt find it, nor did results from the archive
come up.

Thanks CRPence! just installed a v7r1 machine to replicate and indeed it
works like that. So, "No, it's working fine" is the answer.

Thanks!



On Wed, Jul 10, 2013 at 4:08 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 10 Jul 2013 11:16, Roberto José Etcheverry Romero wrote:

I noticed a weird thing on a customer's machine, they use the
QDSPSIGNINF value set to 1, but if they start client access and
authenticate the connection with the same user/pass that they use for
sign on, when the SIGNINF screen comes up, it says the last time the
user logged on was 3 seconds before when authenticating the
connection!
I tried it on one of my machines and it behaves as expected. customer
has v5r4m5 with almost lastest ptf levels (same as my machines). Have
any of you experienced this?
<<SNIP>>

For the *USRPRF defined with DSPSGNINF(*YES), for which the Signon
Information screen will be displayed due to QDSPSGNINF=1, consider...


http://systemicommunity.blogspot.com/2010/06/displaying-previous-sign-on-information.html
Wednesday, June 30, 2010
_i Displaying Previous Sign-On Information i_
"When the QDSPSGNINF is set to one, the Previous Signon Date and Time is
displayed correctly when using Client Access connectivity. The last
date/time of signon for the user profile is updated when the security
API is called to verify a positive indicator and also updates the user
profile. If the password is good for the ID provided, the API returns a
positive indicator and also updates the user profile. There is no
implication that this sign-on was for an interactive job.

The Signon Server for Client Access (for APPC and Sockets) calls the
security API. Other products (such as an OEM emulator) may not call the
security API, for example, Telnet from the DOS prompt. In addition, the
PCOMM product (not the emulator shipped with Client Access) goes
straight to the Telnet server and will not go through the Client Access
Signon Server.
..."

--
Regards, Chuck
--
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.



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.