× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Error CPA3311 when using CPYSPLF
  • From: "York, Albert" <albert.york@xxxxxxxxxxxxxx>
  • Date: Tue, 21 Nov 2000 08:56:57 -0800

I didn't want to affect other jobs so  this is how I solved the problem.

I created a message file in QTEMP then used the MRGMSGF command to copy
CPA3311 to it. I then changed the default reply to G. 

I then used the OVRMSGF command to point to  the message file in QTEMP.

Just before the CPYSPLF command I used the CHGJOB command to change
INQMSGRPY to *DFT

After the CPYSPLF command I changed INQMSGRPY back to *RQD

Albert York     


        -----Original Message-----
        From:   D.BALE@handleman.com [SMTP:D.BALE@handleman.com]
        Sent:   Tuesday, November 21, 2000 7:21 AM
        To:     MIDRANGE-L@midrange.com
        Subject:        Error CPA3311 when using CPYSPLF

        The only way the system reply list gets used is if
INQMSGRPY(*SYSRPYL) is set
        for the job.

        Most shops I've seen leave the default to INQMSGRPY to *RQD.
However, last
        week I ran into a situation on one of our branch boxes where I had a
job fill
        up a file with the maximum number of records (10000 + 1000 * 3) and,
since
        this was a long running job, I added an entry to the system reply
list to keep
        extending the file.  I was surprised when I went to change the job's
INQMSGRPY
        and found that it was already set to *SYSRPYL.  I didn't think much
of it
        until I saw Simon's reply.  I removed my entry for automatically
extending the
        file and found that the job description I was told to use defaults
to use
        INQMSGRPY(*SYSRPYL).  Now I have to find out why.

        So, I guess I would suggest using INQMSGRPY(*SYSRPYL) to solve your
problem,
        but keep mindful that other jobs may be affected if *SYSRPYL is
used.  In this
        particular case, your CPA3311 error should be fairly isolated, don't
you think?

        You can use the CMPDTA parameter in your reply list entry to narrow
down the
        situations where your default reply is applied, but I've never used
this and
        so can't say for certain how it could help you in your particular
situation.

        Dan Bale
        IT - AS/400
        Handleman Company
        248-362-4400  Ext. 4952

        -------------------------- Original Message
--------------------------
        I have a program that uses CPYSPLF to copy a spool file to a data
base file.
        With some spool files I get the error message CPA3311 (Attributes of
file
        not supported). If I answer with 'G' it copies the data that I need.

        Is there any way to prevent this message from coming up? If not is
there any
        way to automatically respond with 'G'? I don't want to add the
message to
        the system reply list. I only want it to default to 'G' in my job.
        +---
        | 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
        +---
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.