RE: Printer override

Check ProgB to see what its Activation group is....  CLP runs in the DAG,
and by default, overrides apply to *ACTGRPDFN, meaning that the override
applies to the activation group that the current program is running.  In
this case, I suspect you program is running in a named activation group, and
the override was applied to *DFTACTGRP.

Easy solutions: 
change the OVRSCOPE parm on the override to *calllvl or *job.
or
eliminate the CLP and issue the override through QCMDEXC within ProgB. 
        
Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: John Furniss [mailto:JFurniss@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, January 06, 2004 1:35 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Printer override


List,
        We have a print file that we've directed to a certain printer
(through CHGPRTF). But this always prints to the user's default printer.
What am I missing? Currently, ProgA calls ProgB which does the printing to
PRTF1. If we change it to have ProgA call CLP1 (containing a printer
override) and have CLP1 call ProgB do we have to pass all parms used in
PRTF1?

        Thanks,

John Furniss
Application Programmer
Allied Machine & Engineering Corp.
jfurniss@xxxxxxxxxxxxxxxxx
(330) 343-4283 ext.8371

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.