remote journaling help

[Former Member]

Hi,

We have 6 partitions. Our PRD partition is almost full and the company says that buying any more disk space right now is not an option. We do have one partition that's only at 31% ASP and I'm wondering how to move our journaling to that other partition. We've been trying to run DBSTATHDB4 on our PRD partition but we don't have enough space to run it due to the tons of journal files it creates.

Thanks!!

Ariel

[Former Member]

Two other areas to consider - dependent on how you use you SAP system. Have you started archiving? If not that could remove some data and hence free up space. Other areas to check are the spool retention periods and also the status of IDOCS (you have to know the business process, but as an example you may have idocs associated with EDI which once processed are no longer required).

[Former Member]

Check some of the other potential space savers, too. It takes a lot to have much impact on an SAP system, since the library is so large, but anything can help:

- old jobs that are hanging around because of unprocessed spool (WRKOUTQ ALL or WRKSPLF SELECT(ALL))

- other journals, besides SAP (WRKJRNRCV ALL/ALL)

- performance data (WRKLIB QMGPDATA, for example)

- make sure your cleanup jobs are running (GO CLEANUP)

Typically, though, these are all in ASP1, which isn't going to help free up space in ASP2, if that's where the journal receivers are. You could set up a process that periodically saves the journal receivers from ASP2 to a savefile in ASP1, then delete the receiver in ASP2. Then, at the end of the day, the savefiles are saved to tape.

You might see if something else ended up in ASP2 accidentally. We occasionally get that if we move a library from one system to another--the default is to put it back in the ASP that it came from. Try

WRKLIB *ALL ASP(2)

[Former Member]

Hi Ariel,

first I assume, that DBSTATHDB4 is large on your site. You should just use CLRPFM on this as described in the note.

Remote journaling "just" replicates the receivers to another box. In order to gain diskspace, you would have to delete your receivers VERY fast, which is not good as well. But, in general it would be possible - set to remote journal and set the local receivers to *autodelete or delete them after any change via program.

btw: you NEED more diskspace in asp1 or 2 ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi Ariel,

Like Volker mentioned, remote journaling would likely not save much storage. Typically the database consumes most of the storage, not the journal receivers.

Is it prossible to allocate more storage to PRD partition by readjusting the LPARs? Consider data archiving and/or reorganizing the database (RGZPFM)?

Thank you,

Victor