View previous topic :: View next topic
|
Author |
Message |
Tebogo23
New User
Joined: 06 Sep 2010 Posts: 5 Location: South Africa
|
|
|
|
Hi
Has anyone automated the newcopy. I am trying to put a step in our endevor compile processor to do newcopy after successfull compilation of the CICS program. This to help programmers not to manually do a newcopy after making changes to their programs:
Below is the step that I have put in to the endevor compile:
//XCF1 EXEC PGM=IEBEDIT, COND(4,LT)
//SYSPRINT DD DUMMY
//SYSUT1 DD DDNAME=IEFRDER
STMT 145 INVALID--KEYWORD DDNAME IS NOT SUPPORTED
//SYSUT2 DD SYSOUT=(A,INTRDR),DCB=BLKSIZE=80
//SYSIN DD DUMMY
//IEFRDER DD *
/*$VS,'F DCICMDA1,CEMT SET PROG(&C1ELEMENT) NEWCOPY' |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
There are advantages to a manual newcopy. The programmer can do an inquiry on the program, do the newcopy, and verify that the program length changed. This allows the programmer to have some confidence that the right library in the DFHRPL concatenation sequence was used for the compile. And if multiple programmers are changing a module, automated newcopy would possibly cause issues where the programmers are not sure which version is installed. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
Why are you using IEBEDIT?
especially since you are not following the required syntax for this utility.
would not a direct EXEC of
whichever 3rd party or IBM utility used to communicate to CICS via batch be a better choice?
there are threads concerning this topic in the forum. just have to search,
instead of posting the same question on two boards (at nearly the same time). not really good 'manners'. |
|
Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006 Posts: 792 Location: Pennsylvania
|
|
|
|
Robert,
We were faced with this decision several years ago.
After a poll of the programmers, seeing the length change and feeling confident was easily displaced with the ease of 'its done'.
We have 15 development libraries and each has it's own cics region.
With the proper concatenation established, we have had virtually no issues with automating the process.
We have also automated newcopies when modules are promoted to the next level for quality testing and production.
Tebgo23,
We use an in house written assembler module (not by me) to perform the newcopy. I am not at liberty to provide this code to you as it does not belong to me.
I was just speaking to my perception of the advantages of automating this process. |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
Back to top |
|
|
Tebogo23
New User
Joined: 06 Sep 2010 Posts: 5 Location: South Africa
|
|
|
|
This is what I have tried lately and the error was sorted out, but when I check the output of the cobol cics it does not give the desired results.
Job11847 $HASP120 INTRDR $VS, 'F DCICMAA!, CEMT SET PROG (&C1ELEMNT) NWECOPY
&C1ELEMNT should be substituted by element name. Please help
Herewith my ammended step:
//STEP1 EXEC PGM=IEBGENER
//SYSPRINT DD DUMMY
//SYSUT2 DD SYSOUT=(A,INTRDR),DCB=BLKSIZE=80
//SYSIN DD DUMMY
//SYSUT1 DD DATA,DLM=$$
/*$VS,'F DCICMAA1,CEMT SET PROG (&C1ELEMNT) NEWCOPY'
$$ |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
|
|
cobtact your local support people, you seem to be struggling and guessing without much success. |
|
Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006 Posts: 792 Location: Pennsylvania
|
|
|
|
Is this just another case of instream data not having the symbolic parameter resolved?
You need another way of passing the program name to be new copied. |
|
Back to top |
|
|
Tebogo23
New User
Joined: 06 Sep 2010 Posts: 5 Location: South Africa
|
|
|
|
Got it right, spelling mistake, &c1elemnt instead of &c1element.
Thank you all.
Best regards |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Good to hear it is working - thank you for letting us know
d |
|
Back to top |
|
|
|