Mch0601 error rc 04 within SEQUEL

850 pts.
Tags:
AS/400
SQL
Is there a SQL cleanup or reset command that I can run to avoid this space offset error? For some reason I can not run a particular sequence of SEQUEL commands. I have two separate applications. I have a script that creates a file, and then uses that file as a view.  Then I have a report definition that I cannot run, maintain or print definition, if I run after the script. Each command of the script, and the commands associated with the report runs at any other point in time. I have combined the steps in one script for testing. After the 4th attempt, the test script  will run without error. As far as the report, I can get it to run if I access any other view or report before. It's only one view based on an output file, and one report to email that I have this problem. Is there a QCLI or SQL command that I can run in between applications to avoid this MCH0601 space offset error? Here are the three SEQUEL commands:
EXECUTE     VIEW(TOMMY/ARBALSTEP1) OUTFILE(QTEMP/ARBALANCE   MBROPT(*REPLACE)  
                                          
SEQUEL/DISPLAY VIEW(TOMMY/ARBALSTEP2)  
                   
 SEQUEL/REPORT REPORT(TOMMY/DSBILLTOP) PCFMT(*PDF) -       
   RECIPIENT('test@gmail.com') OUTQ(*NONE)    
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

Try doing an F1 on the error message. It will usually provide a bit more specific  info on what the actual issue is. From what I have see it could be one of these issues listed on the IBM site for this error code. MCH0601

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Modiyooch
    Already did the F1, poured through the joblogs, and googled. Some explanations don't apply such as:
    "running in same job as BRMS" since we don't have BRMS and the command, Q1AOLD, recommended to clean up the CLI connection does not exist on our system.
    or exceeding 16mb .-> I'm dealing with very small files.
    I cannot identify what is causing it. I suspect it's in third party software. I was hoping for a work around.
    850 pointsBadges:
    report
  • Modiyooch
    I found the cause, but not the reason behind it. All I did was change the name of the alias field.
    SUM(ambal) NAME(sumambal) COLHDG("AMBAL")   to 
    SUM(ambal) NAME(sumbal) COLHDG("AMBAL")  

    Anyone have any incite why this code would throw a MCH0601 error when accessing a report from a different application directly afterwards? I don't believe there is a limitation of 6 characters to an alias name. I believe it's a vendor issue.
    850 pointsBadges:
    report
  • Splat
    Was name sumbal (or sumambal) defined and/or used elsewhere?
    12,895 pointsBadges:
    report
  • Modiyooch
    No, but there was sum(ambal), interesting enough. But, I replaced the name with xumambal and it still had the error; so, it appears it was the length and not the name. I still don't know what was unique about the subsequent report that bombed. No other report bombed.
    850 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: