× 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: PSDS System Date / InternalJobID
  • From: dkeck@xxxxxxx
  • Date: Mon, 21 Aug 2000 20:41:10 US/Eastern

Thanks Mark, 
What I want is the "system date" which is in effect at the time the job entered 
the system (or starts running, either one works).  I want to be able to 
retrieve this static value any time the user activates my utility, even if the 
user's interactive session spans midnight.

Positions 191-198 do not always provide this ... especially when dealing with 
programmers who are testing software.  For example, if I change the job 
description associated with my user profile to show a job date of 010100 and 
sign on to the system, then pos 191-198 yields '01012000', even though the 
system date is August 21.  Likewise, pos 270-275 yield '010100'.  If you change 
the job date while a program is running, then the values in 191-198 and 270-275 
remain static until the program ends with LR on (assuming RPG).  My utility is 
for developers so it must allow for such scenarios (sometimes the utility will 
close with LR on, developer will change the job date, and then the utility will 
be restarted).  Tonight I will test if positions 276-281 remain static across 
midnight.  If so I have my solution.  If not ... then I still have questions 
about that internal job ID... 
We are in agreement on #2 below.  -Dave K

>  |  191  |  198  | Character     | 8     |           | Date (*DATE format)
>  |  270  |  275  | Zoned decimal | 6,0   |           | Date (in UDATE
> 

> This confirms two things:
> 
> 1)  You can use the PSDS to get the date the job started running.  Note,
> that it is not the date the job was submitted, but the date it starts
> running.
> 
> 2)  UDATE is the same date as this date.  In other words, UDATE does NOT
> change after midnight. I know from experience that this is absolutely true.
> If you need the actual date, the TIME op-code is the way to get it.  UDATE
> is always the date the job started running.
> 
> 
> Hope this helps.
> 
> Mark Phippard
> SoftLanding Systems


---------------------------------------------
This message was sent through IDT.
http://www.idt.net/


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

Follow-Ups:

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.