2 Replies Latest reply on Feb 6, 2020 5:08 PM by Heath Robertson

    Control-D batch Print mission query

    Heath Robertson
      Share This:



      I am wanting to have a batch print mission that will do some post processing and formatting of outout before its placed onto the JES output queue for printing...


      I haven't been able to find a way to pass the data from the BATCH Skeleton CTDPRINT step into a temporary dataset, or permanent, for a subsequent step to process.


      Has anyone managed anything like this and how did they do it?


      I have seen;




      None of these options are quite what i had in mind.


      If I can help it I didn't want to need a separate job to post process the seql=filename dataset... option..


      Did I miss somehting buried somewhere in the doco?


      Any ideas appreciated,





        • 1. Re: Control-D batch Print mission query
          Michael Jankowski


          I read your request with interest and am surprised that there are other ControlD customers besides us!

          Thanks for that.


          What kind of data is this? Line Mode or Page Mode data?

          I usually use the CTDAMUTI utility to process my print data. It is also possible to define a Print-2-File Print Mission (CATEGORY SEQL-FILE,NOBANNER) and write the data into a seq.file. In the ControlD Admin Guide you can find some information here.

          1 of 1 people found this helpful
          • 2. Re: Control-D batch Print mission query
            Heath Robertson

            Hi and thanks for your advice...


            I ended up creating a multi-step batch print mission that used the Print mission name as part of the SEQL=file.name.MissName statement


            I then have a PRINT skeleton that has a step that deletes and redefines the output file and refers to the input dataset DSN=file.name.%MISSION%


            I then did my required print format post processing step, before sending output to NPF. But this could be anything  you wanted.


            Final step it to clean up after processing is complete.




            It would be great to be able to refer the Autoedit variables within the JCL that were created/specified in the PRTMIS itself. At this time there are only a very limited set of variables available. And the dataset name length is limited to something like 14 or 15.


            Also I found that you can not use the PRTMIS outclass variable in the batch print skeleton, and this would also be perfect for what we wanted and mean we needed to create fewer PRTMIS batch members.  So I created a different skeleton for every class we needed to print to.


            Only variables that can be  used are;


            //* %DEST%  - PRINT MISSION DESTINATION                            

            //* %UDEST% - PRINT MISSION DESTINATION                            


            //*                                  RUNNING IN PARALLEL).         

            //* %MISSION%  - THE MISSION NAME,                                 

            //* %CATEGORY% - THE MISSION CATEGORY,                             

            //* %GROUP%    - THE MISSION GROUP,                                

            //* %OWNER%    - THE MISSION OWNER ID,                             

            //* %PRTY%     - THE MISSION PRIORITY.                             


            But it all worked as required in the end.