× 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.



Gad, you use the CHGCMD command to set things like prompt override program or VCP.

I am still concerned about changing a system command - IIRC, your change will not survive an update to the OS, for example.

Also, the CRTPRTF and CHGPRTF commands already have both a VCP and a POP - I don't think you want to put your own program there.

So far as I can tell, you are left with using the exit program. Take a look at the first article Mark cited, as well as the IBM documentation - there are or used to be some things to be aware of, such as what happens when you qualify the command with a specific library.

A google search will lead you to other articles on how to use this exit.

BTW, POPs are used typically to display current values for parameters instead of defaults - so that when you do a CHGPRTF, you get the current values from the existing object.

HTH
Vern

On 8/26/2014 12:52 AM, Gad Miron wrote:
Thanks Mark , Vern

I'm familiar with VCP and (to a lesser degree) CMD Exit points
But not with a "prompt override program" which sounds as the simplest way.
How do I attach such a program to CRTPRTF CMD ?



date: Sun, 24 Aug 2014 09:34:07 -0400
from: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
subject: Re: [Bulk] Changhing Default Expiration Date when creating a
Printer file (CRTPRTF)

Gad:

The DAYS parameter on the IBM CHGPRTF command has no default value, as
distributed by IBM, so you cannot change it using CHGCMD. It has always
worked that way.

You can accomplish this by using one or more of the following methods:

1. attach a "prompt override program" to the command to override the
values of "EXPDAT(*DAYS) DAYS(60)"

2. add a validity checking program (VCP) to enforce that DAYS(60) must
be specified.

3. use command processing exit points, QIBM_QCA_RTV_COMMAND, and
QIBM_QCA_CHG_COMMAND. See:
http://www.securemyi.com/articles/artcmdexit1.htm
http://www.securemyi.com/articles/artcmdexit2.htm

HTH,

Mark S. Waterbury

> On 8/24/2014 5:51 AM, Gad Miron wrote:
Hello Guys

In (hopeless?) effort to control the proliferation of old spool files I'm
creating/changing PRTFs with parameters EXPDATE(*DAYS) DAYS(60).
(with a scheduled DLTEXPSPLF CMD to execute once a week).

However, I'm unable to change the DFTs of the CRTPRTF CMD so that
whenever
someone re-create(compiles) a PRTF (using PDM option 14) these
parameters
are lost.
the following CHGCMDDFT CMD(CRTPRTF) NEWDFT('EXPDATE(*DAYS) DAYS(60)')
results in error.

It seems as if NEWDFT('EXPDATE(*DAYS)') is acceptable but not
NEWDFT('DAYS(60)') since I get a CPD6260 "No default value exists for
keyword DAYS" error MSG.

Anyone familiar with it?

Thanks
Gad


------------------------------


date: Sun, 24 Aug 2014 09:21:49 -0500
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: [Bulk] Changhing Default Expiration Date when creating a
Printer file (CRTPRTF)

One other suggestion is to write a command (different name) that may not
have all the parameters of CHGPRTF, and its command-processing program
uses the values Gad wants.

I'm a bit reluctant to add things to system commands, actually. Option 3
below would not do that, but although not really difficult, might seem
daunting to some.

HTH
Vern

On 8/24/2014 8:34 AM, Mark S Waterbury wrote:
Gad:

The DAYS parameter on the IBM CHGPRTF command has no default value, as
distributed by IBM, so you cannot change it using CHGCMD. It has
always worked that way.

You can accomplish this by using one or more of the following methods:

1. attach a "prompt override program" to the command to override the
values of "EXPDAT(*DAYS) DAYS(60)"

2. add a validity checking program (VCP) to enforce that DAYS(60) must
be specified.

3. use command processing exit points, QIBM_QCA_RTV_COMMAND, and
QIBM_QCA_CHG_COMMAND. See:
http://www.securemyi.com/articles/artcmdexit1.htm
http://www.securemyi.com/articles/artcmdexit2.htm

HTH,

Mark S. Waterbury

On 8/24/2014 5:51 AM, Gad Miron wrote:
Hello Guys

In (hopeless?) effort to control the proliferation of old spool files
I'm
creating/changing PRTFs with parameters EXPDATE(*DAYS) DAYS(60).
(with a scheduled DLTEXPSPLF CMD to execute once a week).

However, I'm unable to change the DFTs of the CRTPRTF CMD so that
whenever
someone re-create(compiles) a PRTF (using PDM option 14) these
parameters
are lost.
the following CHGCMDDFT CMD(CRTPRTF) NEWDFT('EXPDATE(*DAYS) DAYS(60)')
results in error.

It seems as if NEWDFT('EXPDATE(*DAYS)') is acceptable but not
NEWDFT('DAYS(60)') since I get a CPD6260 "No default value exists for
keyword DAYS" error MSG.

Anyone familiar with it?

Thanks
Gad





------------------------------

End of MIDRANGE-L Digest, Vol 13, Issue 1333
********************************************



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.