Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Backups Taking Longer

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Backups Taking Longer

    Every so often, on just about every system on the planet, an object that nobody knows about (and everyone swears they had nothing to do with it) gets on the system. These objects tend to be huge, and clog up areas which are normally not used. A quick peak at the WRKSYSSTS or WRKDSKSTS screen can usually determine when available space has diminished. Then comes the detective work of trying to see what, and where this object is. The IFS is a good place to start hunting, but work (temporary) objects in production libraries can also be a problem. Extraordinarily large spool files that never get printed, bloated message queues, undeleted QSYS/QHST* files, distribution objects, etc. may also be culprit candidates. Dave

  • #2
    Backups Taking Longer

    Our operators have complained about the system backup (we use opt. 21) taking longer even though we seem to have about the same about of free disk space and our backups do not use and more tapes than before. Anyone have any ideas why this would be? Thanks.

    Comment


    • #3
      Backups Taking Longer

      This won't be useful to you, but we had a problem where the SAVDLO portion suddenly took twice as long. No obvious reason. Then it went back to normal a couple of weeks later. Both were possibly due to applying PTFs. IBM was unable to figure it out before it cleared itself up. This was at V5R1.

      Comment

      Working...
      X