× 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: Job Date
  • From: Jim Langston <jlangston@xxxxxxxxxxxxxxxx>
  • Date: Tue, 04 Jan 2000 07:40:06 -0800
  • Organization: Conex Global Logistics Services, Inc.

It seemed I typed too quick.  I forgot since it's a S36 PRC it's
actually doing a // JOBQ someprog,somelib.

"Jewel, Jerry" wrote:

> You mentioned you are doing a SBMJOB.  The options for the DATE parm of
> SBMJOB command is:

<SNIP>

I'm on V3R7M0.  Yes, when I do a // DATE or a DATE the session
date is changed.  But, when a // JOBQ batch job is ran, and I display
the batch job, the session date on the batch job is back to the current
system date.

I do not understand how our programs could of worked before this
way, since they are using UDATE which, as I understand it, grabs
the session date.  So before, in my understanding, it had to grab
the changed session date before, but now it doesn't.  There are a lot
of // JOBQ commands in our system, and I am not happy about
having to go about and change every one of them.

"Pat Barber" wrote:
> As you probably know, this is a S/36 command, and I just tested it on
> a V4R3 machine.... It works normally...

> The // date xx/xx/xx changes the "session" date in a S/36EE....

> What release are you on ????

I am probably going to have to find the command syntax for the
// JOBQ command and find out what parameter I need to pass
to it to accept the current session date as the job's session date.

I just don't understand why I would have to change this.  It worked
last Thursday fine.  Today, it doesn't work.  Unless there is something
I am overlooking, but I couldn't image what it could be.

"Wayne Achenbaum" wrote:
> Jim you can put the job date on the DATE parameter on the SBMJOB command
> itself. Then the job will run with the job date specified. The problem you
> are having is that the Date parameter's IBM default is to take the job date
> from  *JOBD which probably points to *SYSVAL which is today's date as does
> QBATCH'S JOBD as an IBM default on V4R4 I'm not sure if it was like that on
> previous releases .

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