Job Date when calling CL/RPG/etc from Java using PCML

Hi,

I have an application where I am kicking off a legacy RPG program from Java
using PCML.  The RPG program is of course hugely complex and would be a lot
of work to rewrite in Java.  This all works fine however I've noticed some
very odd behaviour with the Job Date of the QZRCSRVS that the RPG program
runs in.  What appears to be happening is:

When TCP/IP is started by STRTCP, a QSTRTCP runs for a brief period of time
and submits various other jobs.  We don't IPL our machine very often so
this last ran on 13th Dec 2003.

One of the jobs this kicks off is QZRCSRVSD, which seems to be a job for
servicing Java-to-somethingelse program calls.  This runs with job
description QSYS/QZBSJOBD and since it continuously it unsurprisingly has a
job date of when the job first started, so this is also 13th Dec 2003.

Each time a Java program calls a non-Java program, QZRCSRVSD appears to
kick off a new QZRCSRVS job which again uses job description QSYS/QZBSJOBD.
However what is really odd is that the Job Date on this job is also 13th
Dec 2003.  The Job Date field of the job description says *SYSVAL so it
should just use the value of QDATE but this is definitely not what is
happening.  I'm assuming that somewhere QZRCSRVSD it does a SBMJOB to kick
off the QZRCSRVS job, and on the SBMJOB it specifies a value for Job Date.

This is causing us some major headaches since we rely on Job Date being
today's date.  Ending and restarting TCP/IP each day isn't really a viable
option since this will end all connections to the server.  Does anyone have
any inventive suggestions what we could do to fix this, without having to
alter the RPG program to retrieve today's date in a different way (e.g. by
passing it in as a parameter)?

Thanks very much,

Nigel Gay
Computer Patent Annuities






********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.

If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************