ca.portal.admin

FW: Journal Offload with Fastaccess

Discussion created by ca.portal.admin on Oct 19, 2009
Latest reply on Oct 19, 2009 by ca.portal.admin
Hi David

I ran a quick test to see if I was ""out of date"". No I am not. QSAM does
still work but I was wrong about the Archive being the target for QSAM.
It is actually the input disk journal.

Command =3D=3D=3D> =20
1 RBN processed by OPEN for file J1JRNL =20
30 QSAM BUFFERS will be used =20
QSAM area is ARCHIVE.JOURNAL =20
0 RBN processed by SKIP for file J1JRNL =20
1 RBN processed by QSAM for file J1JRNL =20
.
.
3 RBN processed by WRIT for file J1JRNL =20
3 RBN processed by CLOS for file J1JRNL =20
47,873 pages READ thru QSAM =20
41 pages READ thru BDAM =20
6 pages QSAM skipped =20
30 QSAM BUFFERS used =20
QSAM area is ARCHIVE.JOURNAL =20
=20
END OF JOURNAL ARCHIVE 2009-10-19-11.35.59.820515 =20
Status =3D 0 SQLSTATE =3D 00000 =20

Clearly the process is using QSAM instead of BDAM and it is the input
disk journal which is getting the QSAM push.

The question now is whether the advantages of using QSAM over BDAM have
been eroded over the years by the advances in hardware and caching. It
may well be that when I first tried this solution (in my youth) that the
difference was very marked but that technology has made it redundant.
Neither do I have any recollection of how I came up with 30 as a magic
number.

Chris

=20

Outcomes