Prev
Next
Forums Integration / Customization S3 Customization/Development

New Report Added to Custom Report Program

 8 Replies
 2 Subscribed to this topic
 17 Subscribed to this forum
Sort:
Author
Messages
maalimsimo
Veteran Member
Posts: 49
Veteran Member
1/30/2019 8:51 PM

    After adding a new report to an existing .rpt program, adding the $PRINTFILE XXXXX to the workdef, adding lines to OPEN OUTPUT XXXXX-FILE and CLOSE XXXXX-FILE to the PD, when I run a job I am getting the message "Unable to Open the Output File...". Subsequently, my attempt to write to the Print file results in a longish error message "No XRef for RptSub(3) to iXFFRef file - write ignored....".I probably missed a step somewhere but I am not sure what. Any ideas?

    Ragu Raghavan
    Veteran Member
    Posts: 476
    Veteran Member
    1/30/2019 11:58 PM
      Just out of curiosity, how is the file defined in workdef? print/seq/tape ?
      maalimsimo
      Veteran Member
      Posts: 49
      Veteran Member
      1/31/2019 7:18 PM

        I defined it as 'printer'

        maalimsimo
        Veteran Member
        Posts: 49
        Veteran Member
        1/31/2019 9:07 PM

          I defined it as 'printer'

          Jason Beard
          Veteran Member
          Posts: 124
          Veteran Member
          1/31/2019 9:09 PM

            Did you create a whole new $REPORT section in the .rpt?  Your post seems to imply that you added the $PRINTFILE directive to an existing $REPORT section.

            Jason Beard
            617-548-5568
            jabeard3@gmail.com
            maalimsimo
            Veteran Member
            Posts: 49
            Veteran Member
            2/1/2019 1:21 PM
              Yes, I did. A wholly new fully defined report. rptgen run without any errors, full qcompile is error-free.
              maalimsimo
              Veteran Member
              Posts: 49
              Veteran Member
              2/1/2019 2:26 PM
                Additional info: under batchanim, I can see that the program fails to build the full print file path "$LAWDIR/print///1/, when it calls "BldLocalFileName" USING CRT-PROGRAM-CODE, etc. within the 900-OPEN- procedure. It works well for the older print files.
                Ragu Raghavan
                Veteran Member
                Posts: 476
                Veteran Member
                2/1/2019 2:34 PM
                  Sometimes it helps to delete any existing jobs and try a new one.
                  maalimsimo
                  Veteran Member
                  Posts: 49
                  Veteran Member
                  2/1/2019 3:42 PM
                    You are absolutely right!!!! Deleted it, created a new one and voila! Thanks a bunch