| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Page Dataset increase CSQP017I |
« View previous topic :: View next topic » |
| Author |
Message
|
| terrir |
 Posted: Tue Jan 17, 2006 5:22 am Post subject: Page Dataset increase CSQP017I |
 |
|
Novice
Joined: 11 Jan 2006
Posts: 16
|
We have an application that writes to a queue and causes the page dataset to go into the wonderful world of expansion. This of course causes our threads to be disconnect and basically stops PM4DATA... (in summary)... Right now our page datasets are defined as
DEFINE CLUSTER
(NAME(xxxx.xxxx.PSID01)
RECORDS(10000 500)
LINEAR
VOLUMES(*)
SHAREOPTIONS(2 3) )
DATA
(NAME(xxxx.xxxx.PSID01.DATA)
I want to create a larger page dataset and move this queue to it. What would you guys suggest. Thank you in advance for your help!!!! |
|
| Back to top |
|
 |
| javagate |
| Posted: Tue Jan 17, 2006 5:37 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
read the manual on how to exp the pageset. dont make the secondary space alloc too large. have fun.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Tue Jan 17, 2006 7:52 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
in the manuals there is also a formular so you can calculate how many pages your pageset will need. (planning you rpagesets in concepts and planning guide)
_________________
Regards, Butcher |
|
| Back to top |
|
|
| terrir |
| Posted: Wed Jan 18, 2006 4:49 am Post subject: |
|
|
Novice
Joined: 11 Jan 2006
Posts: 16
|
Thanks for your input.. Time to start formulating!!!!!  |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Sat Feb 11, 2006 4:46 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
If you get near to the VSAM expansion limit of 120+ you could consider getting help from HSM. Stop the queue manager and issue a HBACK (to backup the pageset) and a HMIG (to migrate it) and a HRECALL (to get it back on DASD again).
What VSAM does for you is moving all the extents into the primary allocation, and you're ready to expand 100+ times more.
There are one situatione where this don't help you, and that is if the Pageset tried to expand and could not get the space.
Version 6.0 of WMQ have some new features to avoid the space problems......
There is ofcause the official way to, allocate a new pageset, format it and use COPYPACE and rename ... All documented in the WMQ system admin guid for z/os.
--- Lock it or Lose it --- 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| terrir |
| Posted: Thu Feb 16, 2006 5:33 am Post subject: |
|
|
Novice
Joined: 11 Jan 2006
Posts: 16
|
Thank you for the tips!! We are also working with the vendor that the queue is set up for. They do admit that there is a "little bug", so in the meantime I have created a page set and storage class just for that queue.
Thanks |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
