RE: Processes after CRTSRVPGM -- RPG400-L

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

Lim,

That method tells the system that you are managing the signatures. This is almost the equivalent of setting LVLCHK(*NO) on your files. It gets rid of the error message, but also disables the error checking!

-mark

At 2/13/08 02:14 PM, you wrote:

I personally like the idea of using named signature.

STRPGMEXP PGMLVL(*CURRENT) SIGNATURE('SomeSignatureName')

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Grizzly Malchow
Sent: Wednesday, February 13, 2008 12:49 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Processes after CRTSRVPGM

I am using binder language with *PRV and *CURRENT levels and creating a
new signature every time. It's not ideal but it works. I'll look into
using UPDSRVPGM, when it's applicable, instead of CRTSRVPGM every time.
Thanks

> Are you using binder language? Are you creating a new signature every

>time you add a procedure to a service program? What about when you
>change a procedure's logic (without changing the parameter list)?

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.