× 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: Journal receiver problems
  • From: "ron hawkins" <hwarangron@xxxxxxxx>
  • Date: Tue, 22 May 2001 17:28:30 -0700
  • Importance: Normal



<<For our Information Security department I created numerous programs
collecting data froom the <<Audit jourmals, and creating numerous reports.
This uses the DSPJRN command, and was created in <<V3r7. We are now on V4r3.
These programs have NOT been changed, or recompiled since early 98. So
<<your statement of "It appears that IBM changes the output format of the
DSPJRN command with every <<new release." perplexes me as we hope to convert
to V4r5 soon.

Alan,

We just had this happen again when one of our customers went to V4R5. We
delete the work file and recompile the programs and everything works again.
So perhaps it's a problem with my implementation of the concept. That's why
I was posting to this list in the first place - to see how everybody else
was doing it and if there was a better way. So far, it seems that everyone
is simply doing what we do, recompile and get on with it.

Ron



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.