Does anyone know if BCP ever satisfies this kind of request or should PQ49668 be updated to reflect that this is simply an installation task of MQSeries and always will be?
APAR Identifier ...... PQ49668 Last Changed ........ 01/07/10 ADD CSQYASCP TO PARMLIB MEMBER SCHEDXX. Symptom ...... IN MISSNIG Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 01/07/10 Component .......... 5655F1000 Duplicate of ........ Reported Release ......... 200 Fixed Release ............ Component Name MQSERIES FOR OS Special Notice Current Target Date ..01/07/17 Flags SCP ................... Platform ............ Status Detail: APARCLOSURE - APAR is being closed. ERROR DESCRIPTION: When a OS/390 system is delivery the SCHED member should include all IBM products that run the OS/390 platform. This should include CSQYASCP for MQSeries. LOCAL FIX: This is added during the install of MQSeries. COMMENTS: APAR opened against MQSeries in error. A request has been made to OS/390 to add this in the future. I found this by searching on CSQXJST in the MQ Information Center. http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp Task 4: Update the z/OS program properties table You need to perform this task once for each z/OS system where you want to run WebSphere MQ. If you are using queue-sharing groups, you must ensure that the settings for WebSphere MQ are identical on each z/OS system in the Sysplex. You do not need to perform this task when migrating from a previous version. If it is not already present, you must add the following entry to the program properties table (PPT), which you can find in SYS1.PARMLIB(SCHEDxx). Figure 1. PPT additional entries needed for the WebSphere MQ queue manager PPT PGMNAME(CSQYASCP) /* CSQ - THIS IS REQUIRED FOR WEBSPHERE MQ */ CANCEL /* CAN BE CANCELLED */ KEY(7) /* STORAGE PROTECTION KEY */ SWAP /* PROGRAM IS SWAPPABLE */ NOPRIV /* NOT PRIVILEGED */ DSI /* REQUIRES DATA SET INTEGRITY */ PASS /* NOT ALLOWED TO BYPASS PASS PROT */ SYST /* SYSTEM TASK SO NOT TIMED */ AFF(NONE) /* NO PROCESSOR AFFINITY */ NOPREF /* NO PREFERRED STORAGE FRAMES */ The NOSWAP attribute used in earlier releases of WebSphere MQ is no longer necessary, because the WebSphere MQ queue manager controls swapping itself. However, if you have a heavily-loaded WebSphere MQ network and response time is critical, it might be advantageous to make the WebSphere MQ channel initiator non-swappable, by adding the following further PPT entry, at the risk of impacting the performance of the rest of your z/OS system: Figure 2. PPT additional entries needed for the WebSphere MQ channel initiator PPT PGMNAME(CSQXJST) /* CSQ - MAKE WEBSPHERE MQ MOVER NON-SWAPPABLE */ CANCEL /* CAN BE CANCELLED */ KEY(8) /* STORAGE PROTECTION KEY */ NOSWAP /* PROGRAM IS NON-SWAPPABLE */ Best Regards, Sam Knutson, GEICO Performance and Availability Management mailto:[EMAIL PROTECTED] (office) 301.986.3574 "Think big, act bold, start simple, grow fast..." ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
