In the CA Datacom Datadictionary Batch Reference Guide, the section “DDBTGLM - Generating Batch Transactions › -BTG AUXOUT - Specifying Auxiliary Output Device” (Pg 47 in the PDF version for 14.0, Pg 43 in 15.0) says:
-BTG AUXOUT - Specifying Auxiliary Output Device
Note: You must code this optional transaction before initiating the DDBTGLM utility with either the -BTG or the -BTG START transaction.
However, the sections “DDBTGLM - Generating Batch Transactions › Sample Job Streams and Output › z/OS Example JCL” and “DDBTGLM - Generating Batch Transactions › Sample Job Streams and Output › z/VSE Example JCL” (on Pg 64 in the 14.0 PDF, Pg 58 in 15.0) show the AUXOUT command following the BTG START command, which will not produce the desired output. If the jobs are run using these examples, the SYSPUNCH file will contain the output as normal, but the AUXOUT (or AUXOUTD) file will be empty.
Here is an example of the bad command set (z/OS):
-USR SAMPLE-USER Authorized user information
-DEF PATH,STANDARD
-END
-BTG START,DATABASE,ORDER-ENTRY(PROD),STANDARD
-BTG AUXOUT
-END
And here is what it should be:
-USR SAMPLE-USER Authorized user information
-DEF PATH,STANDARD
-END
-BTG AUXOUT
-BTG START,DATABASE,ORDER-ENTRY(PROD),STANDARD
-END
And likewise, in z/VSE:
-USR SAMPLE-USER Authorized user information
-DEF PATH,STANDARD
-END
-BTG START,DATABASE,ORDER-ENTRY(PROD),STANDARD
-BTG AUXOUTD,SYSNUM=nnn,BLKSZE=nnnn Parms match those in ROSFD
-END
Should be:
-USR SAMPLE-USER Authorized user information
-DEF PATH,STANDARD
-END
-BTG AUXOUTD,SYSNUM=nnn,BLKSZE=nnnn Parms match those in ROSFD
-BTG START,DATABASE,ORDER-ENTRY(PROD),STANDARD
-END
For more information about the BTG utility - DDBTGLM, please refer to the CA Datacom Datadictionary Batch Reference Guide.
As always, please contact CA Technologies support for CA Datacom if you have further questions.