I opened up an etr that went to an apar over a year ago.
It was reportedly fixed, but I proved (again) that it wasn't.
Another apar was opened.
I have just opened an etr (electronic technical response) to check the
status....
apar detail:
(I'm not too happy, at times, with responsiveness of (not support) development
in
1), "breaking" working code at times....
2). not fixing reported problems in a timely manner  (opinion).
FYI Thanks Tim


Item IC24451

  APAR Identifier ...... IC24451       Last Changed..00/09/07
  'BACKUP STORAGEPOOL WAIT=Y' RETURNS RC=0, AFTER IT FAILED


  Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
  Severity ................... 3      Date Closed ......... 00/08/29
  Component .......... 5639A0901      Duplicate of ........
  Reported Release ......... 310      Fixed Release ............ 999
  Component Name ADSM FOR WINDOW      Special Notice
  Current Target Date ..99/10/22      Flags
  SCP ................... PC/DOS
  Platform ............ DOS

  Status Detail: Not Available

  PE PTF List:

  PTF List:
  Release 310   : PTF not available yet


  Parent APAR:
  Child APAR list: IY12950 PQ41315 IC27893 IC27894 PQ41316 IC27895
   PQ41317 IC27896 IC27897 IC27898 PQ41318 IC27899 IC27900 IC27901


  ERROR DESCRIPTION:
  The backup stgpool process was preempted by a higher priority
  process (e.g. a client restore session), when all tape drives
  were in use (ANR1440I). Msg ANR0985I indicated a completion
  state of failure and msg ANR1214I indicated, that not a
  byte was backed up.
  .
  The problem was recreated with AIX4.3.2, server 3.1.2.30


  LOCAL FIX:
  check msg ANR0985I for the completition state of SUCCESS


  PROBLEM SUMMARY:
  ****************************************************************
  * USERS AFFECTED:                                              *
  ADSM V312 Servers for all server platforms.
  TSM V37 and V41 for all server platforms.
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  The BACKUP STGPOOL command with the WAIT=YES parameter
  specified does not return a valid return code in cases where
  the process failed.  The command returns return code 0
  regardless of the outcome of the command.
  ****************************************************************
  * RECOMMENDATION:                                              *
  Apply the ptf containing this fix once it is available.
  ****************************************************************
  The server BACKUP STGPOOL processing has been modified to
  properly report if the process failed.  If it failed, the
  server will now report a non-zero return code to indicate
  the failure.


  PROBLEM CONCLUSION:
  The server process was not able to determine the outcome
  of the backup stgpool process for the purpose of sending
  a meaningful return code.  The process has been altered to
  now report a non-zero return code if there is a failure.


  TEMPORARY FIX:


  COMMENTS:


  MODULES/MACROS:   NONE


  SRLS:      NONE.


  RTN CODES:


  CIRCUMVENTION:


  MESSAGE TO SUBMITTER:




"Mark A. Adams" <[EMAIL PROTECTED]>
11/27/2000 12:12 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>@SMTP@Exchange

To:   [EMAIL PROTECTED]@SMTP@Exchange
cc:

Subject:  Re: Exit Codes from server scripts..

I would be curious too. I have called IBM regarding exit codes for dsmc
command.
Even on a failure it will return zero as the exit code. IBM said that the
product
was working as designed?????????? I always thought if there was an error
that a
greater than zero value was passed. But who am I to say what a return code
should
be.

Any way I got my moaning and groaning down. Back to the subject.

I have a large need to be able to check for a greater than zero value upon a
failure.

Mark Adams

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Bruce Mitchell
Sent: Monday, November 27, 2000 4:25 AM
To: [EMAIL PROTECTED]
Subject: Exit Codes from server scripts..


Does anyone know how  to return an exit code from a server scripts that korn
shell will pick up as non-zero (ie failure)..

Scenario is as per the sample bkup_stg_db scripts (called from KSH). I start
the korn shell script , which checks if a BKUP STGPOOL
process is already running ,and if so reschedule the script for NOW+0:20.
What i want is 'some kind of exit in the reschedule label'  that gets parsed
by ksh as 'not ok'. At the moment the KSH script picks this up as OK ,and
continues rest of script. (Move drm's and prepare). I'm loath to put all
into server scripts , as we want to run the ksh using Control-M scheduler
and catch a result, so thought I'd ask first.


TIA

LONDON
Tel:       +44(0) 207 547 4917
Fax        +44(0) 207 650 7917
Mobile    +44(0) 468 361-885
email:    [EMAIL PROTECTED]



--

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Reply via email to