Now you've got CSL reason codes and can ask help for them, like this: HELP ROUTINES dmsrddbk (ERRORS and look for 54000 if still not found: HELP ROUTINES REASCODE
Some of these PIPE messages sound really alarming. Did you do something special with this SFS server? I didn't have any corrupted SFS file since VM/ESA 1.1 (I had some on VM/SP R6, the release were SFS appeared. I hope you did'n take a DDR backup while SFS was active and restored that, that's asking for corruption. SFS has a tool to check a filepool for errors, but I don't remember the command name. I'd suggest you to contact SW support. 2008/12/23 Wing Chen <[email protected]>: > Thanks for your response. > > By using your command, I got the following messages: > > > For RC = 30: > FPLSFS733E Return code 8 reason code 54000 from DMSRDDBK > FPLMSG003I ... Issued from stage 1 of pipeline 1 > > > For RC = 42: > FPLDBK124E Error reading file: Length of record is 24672 but file has > logical record length > 31 > FPLMSG003I ... Issued from stage 1 of pipeline 1 > > or > > FPLDBK727I 02EF0000 > FPLDBK129E Error reading file: Premature end of file > FPLMSG003I ... Issued from stage 1 of pipeline 1 > > > For RC = 70: > FPLSFS733E Return code 8 reason code 2000 from DMSEXIST > FPLMSG003I ... Issued from stage 1 of pipeline 1 > > Can anyone suggest how to handle for these situations? I would be highly > appreciated if these data file can be recovery. > Thanks. > > -- Kris Buelens, IBM Belgium, VM customer support
