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



That STRCPYSCN command sounds like a nifty idea.

An intermediate solution is to have QSECOFR have a special initial 
program.  That program could do a 
CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES)
and, at the end, 
SIGNOFF LOG(*LIST)
The problem we are having is they'll enter SIGNOFF *NOLIST instead of just 
F3'ing back to exit their initial program.  I am thinking about using the 
command exit program to determine that if it is a person with security to 
do a SIGNOFF LOG(*LIST) whenever SIGNOFF is entered.

Did my first command exit program last week to convert all SNDDST's to 
SNDEMAIL.  Now, with a better default sender, sending to a bad address 
doesn't bring QMSF to it's knees when it tries to reply back to the bogus 
address used by SNDDST.  After some initial headaches, it works quite 
nicely.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





sgallaher@xxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/29/2004 12:02 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Saving a session's history






Is there a 400 equivalent to the old S/36 HISTORY command?

I'm looking for a way to keep track of everything someone did while 
they're signed on with their *SECOFR account (commands, STRSQL sessions, 
etc).  The most detailed thing I can think of is writing some CL to issue 
the STRCPYSCN command when they log in.

Thank you!
 -Scotto
***************************************************************************
The information transmitted is the property of ABM and is intended only 
for the person or entity to which it is addressed and may contain 
confidential and/or privileged material. Statements and opinions expressed 
in this e-mail may not represent those of the company. Any review, 
retransmission, dissemination and other use of, or taking of any action in 
reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please 
contact the sender immediately and delete the material from any computer. 
E-mail transmission cannot be guaranteed to be secured or error-free as 
information could be intercepted, corrupted, lost, destroyed, received 
late or incomplete, or could contain viruses. The sender therefore does 
not accept liability for any error or omission in the contents of this 
message, which arises as a result of e-mail transmission.
_______________________________________________
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 ...

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.