how to identify a cobol program is a dynamic or static call.

lakshmibala · New User Joined: 16 Jun 2004 Posts: 47

hi,
this is an important question asked in ibm chennai.

1) how to identify a cobol program is a dynamic or static call.
give us brief with example.
2) how to move elements from development region to production region.

thanks?ards
lakshmi

bluebird · Active User Joined: 03 Feb 2004 Posts: 127

Dynamic call is specified thru the compiler's parm option :
DYNAM AND on callto the routiine : "in quotes" is dynam.

for your second questrion it depends : is this two phisically separated region (two different MVS systems) or do u mean from test environment to production environment ?
In either case u would need ENDEVOR (or some sort of Version control product) to monitor program versioning

sandip_datta · Posted: Mon Jul 26, 2004 1:50 pm

05 WS-PROGRAM PIC X(08) VALUE 'PROGRAM ' .

CALL WS-PROGRAM is always Dynamic regardless of any compiler option.

CALL "PROGRAM" is dynamic if DYNAM is specified as compiler option.
CALL "PROGRAM" is static if NODYNAM is specified as compiler option.

Regards,
Sandip.

lakshmibala · New User Joined: 16 Jun 2004 Posts: 47

hi

thanks for ur immediate reply.

i meant moving an element from a production region to a development region in endeavour ?

lovingly,

lakshmibala

sandip_datta · Posted: Mon Jul 26, 2004 2:59 pm

Hi Lakshibala,

I am confused !!!!...You want to move elements from production to development or from Development to Production.

Both can be possible through Endevor.

In our shop we prepare Package(option 4) for this movement. Here we have one intermediate stage called UAT. First we move from development to UAT and then from UAT to Production. However for JCLs and parameter we have an option to Transfer elements from development to Production skipping UAT stage. But here also package is involved

For moving elements from production to development we use the endevor utility RETRIEVE (option 2.3).

Regards,
Sandip.

lakshmibala · New User Joined: 16 Jun 2004 Posts: 47

hi sandip,

thanks for ur answer

i wanted to move my element from development region to production region in endeavour -how to do this?

explain clearly

this was asked in one of the interviews

bye with regards,

lakshmibala

lakshmibala · New User Joined: 16 Jun 2004 Posts: 47

hi sandip,

thanks for ur answer

i wanted to move my element from development region to production region in endeavour -how to do this?

explain clearly

this was asked in one of the interviews

bye with regards,

lakshmibala

sandip_datta · Posted: Wed Jul 28, 2004 6:57 am

Hi Lakshmibala,
As I told you, it depends on what version control you are using and which version fo that tool. I think it is sufficient to tell in an interview that in Endevor people prepare package to MOVE/TRANSFER elements from one region to another. After preparation of the package it needs to be approved by Maker(You), Checker(Your manager) and someother authority. After getting approval the package gets executed automatically nd after successfull execution of the package the elements in the package are promoted to different region.

Regards,
Sandip.

lakshmibala · New User Joined: 16 Jun 2004 Posts: 47

hi sandip,

thanks very much for your immediate reply.

bye with regards ,

lakshmi

lakshmibala · New User Joined: 16 Jun 2004 Posts: 47

hi sandip,

what do u mean by version control? and how many versions are in endeavour and what is the currently used version?

let me know totally how many versions are there?

bye with regards ,

lakshmi

sandip_datta · Posted: Wed Jul 28, 2004 3:04 pm

Version control means literaly what it means. In our shop Endevor can store 99 versions of every elements inside it. We can easily retrieve any previous version from there if required.
IBM/CA and other vendors sometimes apply patches and for many other reasons they put extra code in Endevor. Then the version of Endevor is upgraded. This is similar to many other Maniframe products.