Re: Problem with SBMJOB (RPG III)

["Peter Colpaert" <Peter.Colpaert@xxxxxxxxxxxx>]

You could keep a counter in a data area, and add 1 to it every time you
submit a job.  Use the number as a parameter..

This is what I use to create unique member names for work files ('M' + 9
digits).

When the highest value of 999999999 is reached, then the counter restarts
at 1, because normally by that time there will be no more jobs pending of
that long ago.

Hope this helps.

Peter Colpaert
Application Developer
Honda Europe NV
----------
To know recursion, you must first know recursion.
----------




"hrishikesh kotwal" <hdkotwal@hotmail.com>@midrange.com on 13/12/2001
13:56:51

Please respond to rpg400-l@midrange.com

Sent by:  rpg400-l-admin@midrange.com


To:   rpg400-l@midrange.com
cc:

Subject:  Re: Problem with SBMJOB (RPG III)

I adopted your suggested methodology to write a workfile in data library
which
has a primary key of job number. You had also suggested that if more than
one
job was to be submitted from the same interactive session for this process,
then another unique identifier other than the job number, would be
essential.
I need to know which will be the other best unique identifier.

Please advise, your suggestions have helped me see brighter days :-).



Thanks & Regards,

Hrishikesh Kotwal