IEBUPDTE failed to update a record in a member of a PDS,RC=4

vivid8474 · New User Joined: 13 Mar 2008 Posts: 6 Location: CN

This job is to update a record in WISCOB5.INPUT(CTYFILE).

I'd like to replace the first record "WUHAN" with "HANKOU". But the job failed to run with RC=4.

What's the reason? How to make this job executed successfully?

WISCOB5.INPUT(CTYFILE)
---------------------------------------------------------------------------
WUHAN 00010002
SHANGHAI 00020002
GUANGZHOU 00030002
HANGZHOU 00040002
XI'AN 00050002
DALIAN 00060002
BEIJING 00070002
CHENGDU 00080002
---------------------------------------------------------------------------

JCL
----------------------------------------------------------------------------
//VUPDTE JOB '','VIVI',CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),
// NOTIFY=&SYSUID
//CHANGE EXEC PGM=IEBUPDTE
//SYSUT1 DD DSN=WISCOB5.INPUT,DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
./ CHANGE NAME=CTYFILE,UPDATE=INPLACE
WUHAN 00010002
HANKOU 00010002
./ENDUP
----------------------------------------------------------------------------

JOB LOG
----------------------------------------------------------------------------
******************* TOP OF DATA *************************
SYSIN NEW MASTER
./ CHANGE NAME=CTYFILE,UPDATE=INPLACE
WUHAN 00010002
IEB807I INVALID OPERATION.
IEB818I HIGHEST CONDITION CODE WAS 00000004
IEB819I END OF JOB IEBUPDTE.
******************BOTTOM OF DATA **************************
----------------------------------------------------------------------------

CICS Guy · Posted: Tue Apr 08, 2008 6:41 pm

Look a little closer at the manual, Use of the CHANGE function statement without a NUMBER or DELETE detail statement, or a data statement causes an error condition.
And look at the Example 4: Update a Library Member....

Bill Dennis · Posted: Tue Apr 08, 2008 9:20 pm

Your SYSIN should only have the new record, not both records.

vivid8474 · New User Joined: 13 Mar 2008 Posts: 6 Location: CN

Now I have updated my this job as the below two kinds
---------------------------------------------------------------------------------

//VUPDTE JOB '','VIVI',CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),
// NOTIFY=&SYSUID
//CHANGE EXEC PGM=IEBUPDTE,PARM=MOD
//SYSUT1 DD DSN=WISCOB5.INPUT,DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
./ CHANGE NAME=CTYFILE,UPDATE=INPLACE
./ NUMBER SEQ1=ALL,NEW1=00010001,INCR=00000001
HANKOU 00010001
./ENDUP

---------------------------------------------------------------------------------

//VUPDTE JOB '','VIVI',CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),
// NOTIFY=&SYSUID
//CHANGE EXEC PGM=IEBUPDTE,PARM=MOD
//SYSUT1 DD DSN=WISCOB5.INPUT,DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
./ CHANGE NAME=CTYFILE,UPDATE=INPLACE
./ NUMBER SEQ1=ALL,NEW1=00010001,INCR=00000001
WUHAN 00010001
HANKOU 00010001
./ENDUP

---------------------------------------------------------------------------------

But the RC is still 4, the log as the below:
---------------------------------------------------------------------------------

********************************* TOP OF DATA **********
SYSIN NEW MASTER
./ CHANGE NAME=CTYFILE,UPDATE=INPLACE
./ NUMBER SEQ1=ALL,NEW1=00010001,INCR=00000001
HANKOU
IEB807I INVALID OPERATION.
IEB818I HIGHEST CONDITION CODE WAS 00000004
IEB819I END OF JOB IEBUPDTE.
******************************** BOTTOM OF DATA ********
---------------------------------------------------------------------------------

gcicchet · Posted: Wed Apr 09, 2008 7:29 am

Hi,
try this

superk · Posted: Wed Apr 09, 2008 8:14 am

This is interesting. I don't think I've ever seen someone actually use IEBUPDTE like this, instead of an edit or SORT.

gcicchet · Posted: Wed Apr 09, 2008 8:33 am

Hi,
this is how JCL, PROCS were updated in the good old punch card days (haha)

Gerry

vivid8474 · New User Joined: 13 Mar 2008 Posts: 6 Location: CN

Problem still exists with RC=4

Now this job is updated to as the below:

gcicchet · Posted: Wed Apr 09, 2008 8:56 am

Hi,
can you please post the JCL using Code.

Gerry

Bill Dennis · Posted: Wed Apr 09, 2008 8:19 pm

I don't know why you've added parms to reassign SEQ numbers? If you're only replacing one line of the member, remove the NEW1 and INCR options.

gcicchet · Posted: Wed Apr 09, 2008 9:20 pm

Hi Vivid8474,
the problem is with the ./ENDUP it requires a space after the ./ as im my example previously mentioned. ie.

vivid8474 · New User Joined: 13 Mar 2008 Posts: 6 Location: CN

ok. it got solved.

Thx, all~~

nandhu · New User Joined: 07 Mar 2006 Posts: 7 Location: chennai

Hi,

One of our production job has the following step and it ended with RC 04.

JOB:

//INSTP30 EXEC PGM=IEBUPDTE,
// PARM=MOD
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=H1279AF.CODE.COMPARE.PROD,DISP=OLD
//SYSUT2 DD DSN=H1279AF.CODE.COMPARE.PROD,DISP=OLD
//SYSIN DD DSN=H1279AF.IEBUPDTE.INPUT,DISP=OLD
/*

SYSIN:

./ CHANGE NAME=PUV07I,UPDATE=INPLACE
ISRSUPC
AAAAAAA
./ ENDUP

The below is the sysprint:

.SARPAGE 10 DS=SYSPRINT.INSTP30 . /0000134
. SYSIN NEW MASTER
. ./ ENDUP
.IEB805I CONTROL STATEMENT ERROR.
.IEB818I HIGHEST CONDITION CODE WAS 00000004
.IEB819I END OF JOB IEBUPDTE.

I refered to one of the previous topic and as per the above discussion, it was mentioned there should be one space before and after ENDUP in the sysin card. The sysin we use has space and still we get the rc 04.

Could anyone please help us in resolving this error?

dick scherrer · Posted: Sat May 16, 2009 1:14 pm

Hello,

It will help us help you if you post output that is from the posted input. . .

The "sysprint" does not appear to have been created from the posted sysin.

Suggest you practice using the "Code" tag which will make posting jcl, control statements, code, and data much more readable.

Also, at the top of the pager is a link to "IBM Manuals" one of which is the "IBM JCL Utilities Guide for DFSMS". This has the information on the iebupdte utility.

Does the job possibly have multiple steps?

nandhu · New User Joined: 07 Mar 2006 Posts: 7 Location: chennai

Hi Dick,

yes, this job has multiple steps and this step has returned 04. My previous posting was the job we tried in test region.

The prod job's sys in had no statements except ENDUP. I tried going through the manuals, but couldn't resolve it.

Code:

dick scherrer · Posted: Mon May 18, 2009 11:27 am

Hello,

Please post the sysprint output of thie instp30. Also please post the jcl, sysin, and sysprint for a step that works as needed.

Note how your previous post has now been "Coded". With a little practice, it becomes almost automatic. It also preserves alignment, so the poster does not have to count positions

nandhu · New User Joined: 07 Mar 2006 Posts: 7 Location: chennai

Hi,

Please find below the sysprint of the above step:

gcicchet · Posted: Wed May 20, 2009 5:26 am

Hi,

I'm a little confused with this thread, what exactly are you trying to achieve ?

nandhu · New User Joined: 07 Mar 2006 Posts: 7 Location: chennai

Hi,

This job step now is a dummy step, we will be adding the functions when ever we want change something in a library. This library has the copybook structure of some tables. So only when we change/add some copybooks we update the sysin with appropriate commands.

So when there is no change, this step is a dummy step and should return zero, but now it throws an error saying control statemetn error.

dick scherrer · Posted: Thu May 21, 2009 7:55 pm

Hello,

You should re-think the implementation. . .

You need to make sure there is "something" to update even if it is a dummy member or set/use a condition code to conditionally execute this step only when there is something to update.

IBM is not going to change the utility to do what you are trying to do.