We nearly(!) solved this problem.
The development process at our customer is:
Development with SAS(NT) -> Upload to host (SAS6.09)
The last time the program source was changed when
they still used 6.08 (Windows3.x).
With this Version the program works fine after uploading to host.
Compiled with 6.12 the program fails working correctly on SAS 6.09 (MVS).
We found, that after compiling with 6.12 the >8 blanks in the CONFIG-lines
are reduced to 1 blank!!
So the DD Statements are not at the place where they should be.
Under 6.08 the blanks are still there.
Why does the compiler (?) try to "optimize" the code within a submit-block ?
> Hi everybody !
> I'm trying to submit a batch job-JCL that must have the following form:
> // ...<some JCL statements>
> // SASLIST DD ...<something>
> // CONFIG DD
> // DD
> // DD *
> // ALTPRINT=SASLIST
> // SYSIN *
> // <SAS code follows>
> When submitted directly in EJES the job does what I expected.
> When "stepwise building" this job in an AF (SCL)-program
> with SUBMIT-ENSUBMIT blocks and finally
> sending the preview buffer for execution
> the jcl is not correct(?). Instead of one SYSIN-Step there
> are 2 steps generated (one with the ALTPRINT, the other one with
> the SAS-Code).
> Obviously the SAS code is not processed.
> (Due to the Installation, the JCL-Job has to be exactly in the form shown
> above !
> I don't know exactly, why the "empty" CONFIG DD -Statements have to be
> Probally something in the CLIST ?)
> Any suggestions ?
> Dipl.-Inform. Thies Meyer
> EMail : email@example.com
> Phone: (+49)-171-8314215
> Fax : (+49)-171-13-8314215