Re: *dtaara in *srvpgm

Phil,  Drop the "u" on your first d-spec and it will work.  The "u" makes
this a "data area data structure", which will by definition be automatically
opened when the program starts and automatically updated and closed when the
program ends.  -Dave K.

----- Original Message -----
From: "Phil" <sublime78ska@attbi.com>
To: <rpg400-l@midrange.com>
Sent: Thursday, June 20, 2002 8:18 PM
Subject: *dtaara in *srvpgm


> Oops, forgot to change the subject.
>
> Sorry,
> Phil
>
> > -----Original Message-----
> > From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
> > Behalf Of Phil
> > Sent: Thursday, June 20, 2002 8:10 PM
> > To: rpg400-l@midrange.com
> > Subject: RE: Pointer Question
> >
> >
> > All,
> >
> > I'm using a data area in a service pgm.  It is defined outside of all
the
> > procedures.
> >
> >      H nomain
> >      D cgi_libr       uds                  dtaara(cgilibda)
> >      D  cgi_lib                1     10
> >
> > Inside the procedure, I have this:
> >
> >
> >      C                   in(e)     cgi_libr
> >
> > Normally this doesn't lock the data area, but the compiler gives me a
> > warning that I should also use OUT when nomain is specified.  OK, I'll
do
> > it.
> >
> > When the srvpgm, which is in a named activation group, runs the first
time
> > ok.  But the second call in the same job I get this error:
> >
> > RNX0412 Data area CGILIBDA is not allocated for output.  There's
> > no updating
> > going on.  Before I added the e extender, I was getting a *LOCK not
> > satisfied error (didn't keep the msgid.).
> >
> > Is this something I can't do with service pgms?  Or have I overlooked
> > something obvious which once pointed out will make me ashamed? :)
> >
> > This as400 is at V4R4.
> >
> > Thanks for your help,
> >
> > Phil
> >
> >
> >
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>