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


  • Subject: RE: LDA Changes L#USER, L#TERM
  • From: "May, Lori" <LMay@xxxxxxxxxxxxxxxxx>
  • Date: Thu, 12 Apr 2001 05:29:20 -0400

Title: RE: LDA Changes L#USER, L#TERM

According to GEAC, this has been fixed in Service Pak 4, which should be available in late May.

LMay

-----Original Message-----
From: Heffner, Art [mailto:AHeffne@PTS-TOOLS.COM]
Sent: Wednesday, April 11, 2001 3:46 PM
To: jbausers
Subject: LDA Changes L#USER, L#TERM


We have just found this problem and wonder if anyone else has experienced
it.

When leaving the G/L journal posting option, User name changes at the top of
the menu and this new user's security is used for menu authorizations.  If
you display the LDA, the L#USER # and L#TERM fields have been changed to a
user with an open cash posting session or 3 way match session.  If you
display the job using Sysreq 3 the original user and terminal ID is still
signed on according to the IBM operating system.

I am also wondering if this could have anything to do with skipped sessions,
lockups, etc.  We are on 3.5.1.

Art Heffner
Production Tool Supply

+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---


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.