Rexx scripts to monitor PDS

premkrishnan · Active User Joined: 07 Sep 2006 Posts: 135 Location: Mars

Hi,

Our system has a library which has load modules

Is it possible to monitor a monitor this PDS through some rexx scripts then submit one job if the member was starting with abcd* was moved happened to those PDS.

If the member which was moved started with abdc* i need to submit a bind job having program as abcd* which is through some rexx script or any alternative.

I am familiar to rexx but this requirement looks complicated for me.If can anyone guide me how to go about it it will be helpful

Please let me know your comments.

enrico-sorichetti

NO

if Your development is done in a controlled environment ( SCLM, ENDEVOR, CHANGEMAN, ...)
and the setup has been done properly
the rebind should take place automatically at each build/promote

I can guarantee that for SCLM ( done it )
but I suppose that it should be true also for the other programs
( it' s a very basic function )

premkrishnan · Active User Joined: 07 Sep 2006 Posts: 135 Location: Mars

Actually we use ENDEVOR and as we move the element we dont use

BYPASS ELEMENT DELETE

But as we the move doesnt happen through us we cant avoid them being deleted from lower libraries

So all the program being moved gets deleted from lower libs.

so if we missed to do a rebind for the same in lower libs the job fails for
-805

So I thought which will help reduce these issues.

enrico-sorichetti

never happened to me with SCLM, I guess it is a setup issue

I' ll just show the logic with two levels only TEST and PROD

You have a program PROG1
when You build at the TEST level You obtain trhu compiler and lked
a DBRM and a LOAD_MODULE
and an additional step will bind to the test db2 environment
the control info in the dbrm an load module is in sync

when promoting to the higher level
all the involved components are moved from the
from the <TEST>.stuff to the <PROD>.stuff

source,load,dbrm
and a bind step is run to bind to the prod db2 environment
since the DBRM and the LOAD are not changed ( a relink does not chage the DB2 control info )

You can run the prod load modulee on the test db2 with no problem

it would be better to get a better understanding of the whole process and setup

premkrishnan · Active User Joined: 07 Sep 2006 Posts: 135 Location: Mars

Thanks enrico sorichetti

When we move the element from the <TEST>.stuff to the <PROD>.stuff

The loadlib and dbrm gets deleted through endevour.

But I as you said its should be something to do with the setup..

I will try to figure it out and meanwhile if anyone knew the setup which we need to take care for bind in lower regions though ENDEVOR please let me know.

enrico-sorichetti

You misunderstood

if the setup has been done properly
there is no ned to rebind at the lower level

if it were so You would need to rebind at all levels of the development hierarchy

premkrishnan · Active User Joined: 07 Sep 2006 Posts: 135 Location: Mars

Got it now

BYPASS ELEMENT DELETE

To Avoid that this is the only go

enrico-sorichetti

an issue would be if the load module was not copied but rebuilt from the sources ( creating a new dbrm )
in this case the whole environment would be out of sync
rebuilding from the sources at any level would invalidate the contokens at the lower levels

i would repeat again if the setup is proper You can delete the lower level on promotion with no issues

review the setup with the endevor support group

premkrishnan · Active User Joined: 07 Sep 2006 Posts: 135 Location: Mars

Thanks enrico sorichetti

Will do that.....