×
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.
Dean.Eshleman wrote:
Problem solved! Another developer here tried to do this and it
worked for them. Then, I remembered that the routing data on the
job description I was using was setup to use a compile
preprocessor. When I switched to a different job description that
had the normal routing data (QCMDI), then it worked as expected.
To bad I didn't think of that sooner.
So there is a documented restriction on the feature of the
CPYENVVAR(*YES) for SBMJOB, that the routing must use RTGDTA(QCMDI)
or perhaps that QCMD is the request processor? That would seem like
a pretty huge unstated limitation on a feature that is generically
described as determining "whether the environment variables from the
submitting job are copied to the new job." The control is at the
point of submission, so why would the point of entry per routing
have any relevance as to the availability of that data? I would
consider the condition of the "copied" data being unavailable in the
"new job" to be a defect; i.e. they were not really copied.
Regards, Chuck
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.
midrange.com
