RE: Error CPA3311 when using CPYSPLF

I thought of that but, unfortunately, the job name in the message data is
the name of the job that produced the spool file, not the current job. In
this case they are different. That means I would have to use the CHGRPYLE
command before every CPYSPLF command. I decided it would be just as easy to
use the CHGJOB command and specify INQMSGRPY(*DFT) instead. That way, my job
is protected against unintended consequences caused by other reply list
entries.

To my mind, the system reply list is too generic. When you change your job
to use the system reply list it applies to all of the entries. This can
cause problems if you don't have total control over the contents of the
system reply list. What I would like is a 'job reply list' or a way of
saying that specific system reply list entries only apply to this job (or
this user) and to  only use those entries when running this job. Perhaps
allowing multiple reply lists with different names instead of just one.
 
Albert York
        
        -----Original Message-----
        From:   Pete Hall [SMTP:pbhall@execpc.com]
        Sent:   Wednesday, November 22, 2000 5:38 PM
        To:     MIDRANGE-L@midrange.com
        Subject:        RE: Error CPA3311 when using CPYSPLF

        At 18:35 11/21/2000, Albert York wrote:

        >         How do you set up the filter to do that?

        Looking at CPA3311 in WRKMSGD, gives you the data elements:

                                  Display Formatted Message 
        Text
        
System: 
        SYSTEMB
          Message ID . . . . . . . . . 
        :   CPA3311
          Message file . . . . . . . . 
        :   QCPFMSG
            Library  . . . . . . . . . 
        :     QSYS

          Message . . . . :   Attributes of file &1 not supported.  (G 
        C)
          Cause . . . . . :   The Copy Spooled File (CPYSPLF) command found 
        special
            device requirements of file &1 number &2 job &5/&4/&3. The
attributes 
        that
            are not copied by the CPYSPLF command are defined characters, 
        transparency,
            variable characters per inch (CPI), variable lines per inch
(LPI), 
        variable
            font, variable character identifier (CHRID), subscript and 
        superscript,
            graphics functions, variable page rotation, enhanced 3812 fonts,
bar 
        codes,
            intelligent printer data stream (IPDS) transparent data, and
some final 
        form
            text 
        functions.
              Attributes that are simulated by CPYSPLF are highlight and
some final 
        form
            text 
        function.
          Recovery  . . . :   Type G to continue or C to cancel the copy 
        request.  If G
            is entered, the results may not be acceptable 
        because:
        
More... 


        Looking at the field data gives you the positions in the MSGDTA
buffer:

                                        Display Field Data

          Message ID . . . . . . . . . :   CPA3311
          Message file . . . . . . . . :   QCPFMSG
            Library  . . . . . . . . . :     QSYS


                                              Decimal       Vary
          Field     Data Type     Length     Positions     Length     Dump
           &1       *CHAR            10                               *NO
           &2       *BIN              2                               *NO
           &3       *CHAR            10                               *NO
           &4       *CHAR            10                               *NO
           &5       *CHAR             6                               *NO

        If you wanted to condition the action based on the job name, that
would be 
        &3, which starts at buffer position 13, and is 10 bytes in length,
so you 
        could specify something like this:

           ADDRPYLE SEQNBR(999)
                    MSGID(CPA3311)
                    CMPDTA('MYJOB     ' 13)
                    RPY(G)

        HTH
        Pete

        Pete Hall
        pbhall@execpc.com
        http://www.execpc.com/~pbhall/

        
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---