UPGRADE: PSFVM210 INTRODUCTORY TEXT PG 001 OF 076 ************************ * UPGRADE PSFVM210 * ************************ THIS UPGRADE CONTAINS INSTALLATION INFORMATION AND/OR HIGH IMPACT/PERVASIVE APAR INFORMATION FOR VERSION 2, RELEASE 1, MODIFICATION 0 FOR PRINT SERVICES FACILITY (PSF) ************************************************************************ * P R O D U C T I N D E X * ************************************************************************ PID NUMBER SYSTEM DESCRIPTION SUBSET ID 5684141 VM PSF R210 VM/210 UPGRADE: PSFVM210 ADDITIONAL TEXT PG 002 OF 076 HIGH IMPACT/PERVASIVE (HIPER) APAR INSTRUCTIONS Included in this upgrade may be one or more apars that describe problems that are of a high impact or extremely pervasive nature. The following fields provide an outline of those APARs in SECTION 4: "PROBLEM:" A brief description of the APAR "USERS AFFECTED:" If you have this product/device/situation, you are exposed to the problem. "RECOMMENDATION:" Take action that is described. Most often that will be the application of an APAR or PTF fix. VOLID'S VOLID 1000 - Reflects corrective service (not on a PUT tape) UPGRADE: PSFVM210 ADDITIONAL TEXT PG 003 OF 076 VOLID 9XXX - Reflects a PUT tape that the PTF can be located on. CLARIFICATION OF SUP LEVELS A sup level for a subset is represented by a subset name, a slash, and a put level number. (ex: Subset/9104) Please note that a sup level does not represent a put level. It is not labeled as a put because in reality it is a put level + 2 Levels higher of 'reach ahead' service. ** BEWARE ** Do not apply a put tape on top of a SUP tape unless the PUT level is 3 levels higher. Applying a put tape that is not 3 levels higher could cause regression. UPGRADE: PSFVM210 ADDITIONAL TEXT PG 004 OF 076 UPGRADE: PSFVM210 SUBSET: CHG/INDEX INTRODUCTORY TEXT PG 005 OF 076 ******************** * SUBSET CHG/INDEX * ******************** THE PURPOSE OF THIS SUBSET IS TO TRACK ALTERATIONS TO THE VARIOUS ELEMENTS OF THIS UPGRADE. *********************************************************************** * C H A N G E I N D E X * *********************************************************************** DATE SUBSET ALTERED COMMENTS 63. 99/04/23 VM/210 SECTION 3, ADDED ITEM 37 62. 99/03/22 VM/210 SECTION 2, ADDED ITEM 5 VM/211 SECTION 2, ADDED ITEM 5 61. 98/03/26 VM/210 SECTION 3, ADDED ITEM 36 60. 98/03/26 VM/210 SECTION 3, ADDED ITEM 34 35 59. 98/01/20 VM/210 SECTION 3, ADDED ITEM 33 UPGRADE: PSFVM210 SUBSET: CHG/INDEX INTRODUCTORY TEXT PG 006 OF 076 58 97/12/10 VM/210 SECTION 4, ADDED ITEM 19 PQ09099 UQ12280 57 97/12/05 VM/210 SECTION 4, ADDED ITEM 17 PQ06815 UQ08287 VM/210 SECTION 4, ADDED ITEM 18 PQ06815 UQ08286 56. 96/04/18 VM/210 SECTION 3, ADDED ITEM 32 55. 96/02/22 VM/210 SECTION 3, ADDED ITEM 31 54. 95/01/27 VM/210 SECTION 1, ADDED ITEM 2 53. 94/12/01 VM/210 SECTION 3, ADDED ITEM 30 52. 94/07/19 VM/210 SECTION 3, ADDED ITEM 29 51. 94/03/01 VM/210 SECTION 3, UPDATED ITEM 17 50. 93/09/02 VM/210 SECTION 3, ADDED ITEM 28 49 93/08/10 VM/210 SECTION 4, ADDED ITEM 16 PN43123 UN47233 48 93/08/10 VM/210 SECTION 4, ADDED ITEM 15 PN43123 UN47232 47 93/08/10 VM/210 SECTION 4, ADDED ITEM 14 PN43123 UN47231 46 93/08/10 VM/210 SECTION 4, ADDED ITEM 13 PN43123 UN47230 45 93/08/10 VM/210 SECTION 4, ADDED ITEM 12 PN43123 UN47229 44 93/08/10 VM/210 SECTION 4, ADDED ITEM 11 PN43123 UN47228 43 93/08/06 VM/210 SECTION 4, ADDED ITEM 10 PN38057 UN44283 42 93/08/06 VM/210 SECTION 4, ADDED ITEM 9 PN38057 UN44282 41 93/08/06 VM/210 SECTION 4, ADDED ITEM 8 PN38057 UN44281 UPGRADE: PSFVM210 SUBSET: CHG/INDEX INTRODUCTORY TEXT PG 007 OF 076 40 93/08/06 VM/210 SECTION 4, ADDED ITEM 7 PN38057 UN44280 39 93/08/06 VM/210 SECTION 4, ADDED ITEM 6 PN38057 UN44279 38 93/08/06 VM/210 SECTION 4, ADDED ITEM 5 PN38057 UN44278 37. 93/02/26 VM/210 SECTION 3, ADDED ITEM 27 36. 93/01/08 VM/210 SECTION 2, ADDED ITEM 4 35. 92/10/08 VM/210 SECTION 3, ADDED ITEM 26 34. 92/09/28 VM/210 SECTION 5, ADDED ITEM 4 33. 92/09/18 VM/210 SECTION 5, ADDED ITEM 3 32. 92/09/04 VM/210 SECTION 3, ADDED ITEM 25 31. 92/08/25 VM/210 SECTION 3, ADDED ITEM 24 30. 92/08/19 VM/210 SECTION 2, ADDED ITEM 3 29. 92/08/07 VM/210 SECTION 5, ADDED ITEM 2 28. 92/08/03 VM/210 SECTION 2, ADDED ITEM 2 27. 92/07/27 VM/210 SECTION 3, ADDED ITEM 23 26. 92/04/06 VM/210 SECTION 3, ADDED ITEM 22 25. 92/04/06 VM/210 SECTION 2, ADDED ITEM 1 24 92/03/16 VM/210 SECTION 4, ADDED ITEM 4 PN08536 UN09958 23. 92/03/03 VM/210 SECTION 3, ADDED ITEMS 21 22. 92/02/17 VM/210 SECTION 3, ADDED ITEMS 20 UPGRADE: PSFVM210 SUBSET: CHG/INDEX INTRODUCTORY TEXT PG 008 OF 076 21. 92/01/31 VM/210 SECTION 3, ADDED ITEMS 18-19 20 92/01/23 VM/210 SECTION 3, ADDED ITEM 17 19 91/11/26 VM/210 SECTION 4, ADDED ITEM 3 PL83703 UL97732 VM/210 SECTION 3, ADDED ITEM 16 18. 91/11/21 VM/210 SECTION 3, ADDED ITEM 15 17. 91/11/14 VM/210 SECTION 4, DELETED ITEMS 1-2 16. 91/11/13 VM/210 SECTION 4, ADDED ITEMS 1-2 15. 91/09/25 VM/210 SECTION 1, ADDED ITEM 1 14. 91/09/24 VM/210 SECTION 3, ADDED ITEM 14 13. 91/09/09 VM/210 SECTION 5, UPDATED ITEM 1 12. 91/09/06 VM/210 SECTION 5, ADDED ITEM 1 11. 91/08/07 VM/210 SECTION 3, ADDED ITEM 13 10. 91/07/29 VM/210 SECTION 3, ADDED ITEM 12 9. 91/07/26 VM/210 SECTION 3, UPDATED ITEM 4 8. 91/07/17 VM/210 SECTION 3, ADDED ITEM 11 7. 91/05/30 VM/210 SECTION 3, ADDED ITEMS 9-10 6. 91/05/24 VM/210 SECTION 3, ADDED ITEM 8 5. 91/05/23 VM/210 SECTION 3, ADDED ITEM 7 4. 91/05/16 VM/210 SECTION 3, UPDATED ITEM 1 UPGRADE: PSFVM210 SUBSET: CHG/INDEX INTRODUCTORY TEXT PG 009 OF 076 VM/210 SECTION 3, ADDED ITEM 6 3. 91/05/05 VM/210 SECTION 3, ADDED ITEM 5 SECTION 3, UPDATED ITEM 1 2. 91/04/18 VM/210 SECTION 3, ADDED ITEMS 1-4 1. 90/10/24 UPGRADE/SUBSET CREATED - SMRG UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 010 OF 076 *********************** * SUBSET VM/210 * *********************** THIS SUBSET CONTAINS INSTALLATION INFORMATION FOR PRINT SERVICES FACILITY (PSF), VERSION 2, RELEASE 1, MODIFICATION 0 FOR VM ************************************************************************ * C H A N G E S U M M A R Y * ************************************************************************ DATE LAST CHANGED SECTION 1. 95/01/27 INSTALLATION INFORMATION 2. 99/03/22 DOCUMENTATION CHANGES 3. 99/04/23 GENERAL INFORMATION 4. 97/12/10 SERVICE RECOMMENDATIONS 5. 92/09/18 CROSS PRODUCT DEPENDENCIES UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 011 OF 076 SERVICE RECOMMENDATION SUMMARY DATE APAR PTF VOLID COMMENTS 19 97/12/10 PQ09099 UQ12280 1000 HIPER PRINT JOB HANGS USING CUT 18 97/12/05 PQ06815 UQ08286 1000 HIPER SLOW PERFORMANCE, BLANK 17 97/12/05 PQ06815 UQ08287 1000 HIPER SLOW PERFORMANCE, BLANK 16 93/08/10 PN43123 UN47233 9401 PTFSERVA PTFSERVL PTFSERVV 15 93/08/10 PN43123 UN47232 9401 PTFSERVA PTFSERVL PTFSERVV 14 93/08/10 PN43123 UN47231 9401 PTFSERVA PTFSERVL PTFSERVV 13 93/08/10 PN43123 UN47230 9401 PTFSERVA PTFSERVL PTFSERVV 12 93/08/10 PN43123 UN47229 9401 PTFSERVA PTFSERVL PTFSERVV 11 93/08/10 PN43123 UN47228 9401 PTFSERVA PTFSERVL PTFSERVV 10 93/08/06 PN38057 UN44283 9401 ADD SUPPORT FOR ACIF AND AFP 9 93/08/06 PN38057 UN44282 9401 ADD SUPPORT FOR ACIF AND AFP 8 93/08/06 PN38057 UN44281 9401 ADD SUPPORT FOR ACIF AND AFP 7 93/08/06 PN38057 UN44280 9401 ADD SUPPORT FOR ACIF AND AFP 6 93/08/06 PN38057 UN44279 9401 ADD SUPPORT FOR ACIF AND AFP 5 93/08/06 PN38057 UN44278 9305 ADD SUPPORT FOR ACIF AND AFP UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 012 OF 076 4 92/03/16 PN08536 UN09958 9201 SFCM PERIODICALLY NEEDS AUDIT 3 91/11/26 PL83703 UL97732 9105 PRINTING A GERMAN CHARACTER 2. 91/11/13 PN09147 ITEM DELETED 91/11/14 1. 91/11/13 PN03986 ITEM DELETED 91/11/14 ************************************************************************ * SECTION 1. I N S T A L L A T I O N I N F O R M A T I O N * ************************************************************************ THIS SECTION CONTAINS CHANGES TO THE PRODUCT'S PROGRAM DIRECTORY. 2. 95/01/27 See apar PN18912 (attached) for information when loading fonts. 1. 91/09/25 PAGE 19, SECTION 5.1.2 TARGET SYSTEM REQUIREMENTS OF THE PSF/VM PROGRAM DIRECTORY (G544-3683-00) SHOULD BE UPDATED TO READ: "IBM 3828 REQUIRES EC C06145 (OR HIGHER)" "IBM 3900 REQUIRES EC C14194 (OR HIGHER)" UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 013 OF 076 ************************************************************************ * SECTION 2. D O C U M E N T A T I O N C H A N G E S * ************************************************************************ THIS SECTION OUTLINES MAJOR ERRORS IN THE PRODUCT'S PUBLISHED DOCUMENTATION. 5. 99/03/22 'After applying PQ18523 if you are running the SFCM in a DCSS it will abend and loop doing an IPL. The DCSS is no longer large enough. You must define the DCSS size to be 800-8D0. See doc apar PQ25028 for more info.' 4. 93/01/08 Installing D/T4028 IVP, no print out, no error message, V5684141 PSF/VM SYSTEM PROGRAMMING GUIDE S5443680-00 chapter 5 page 189 fig.34 See DOC APAR PN05808 (attached) 3. 92/08/17 GRP3 DCSS overflowed after applying maintenance. Received UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 014 OF 076 MSDMSITP141T - operation exception occurred at x'000006' in routine APRINIT, and MSAPRABN559T - system abend code x'0C1.' The PSF/VM Program Directory is in error. See DOC APAR PN26757 (attached). 2. 92/08/03 S544-3680-00 PSF/VM System Programming Guide page 221. All PSF/VM 2.1.0 customers who create their own SFCM installation exits. See APAR PN25215 (attached) for more information. 1. 92/04/06 The PSF/VM 2.1.0 Program Directory (G544-3683-00) has a error on pages 68-69. The Group3 PDM DCSS (APRGP34D) does NOT need to be identified to GCS using the SEGMENT macro. Therefore the bottom 2/3 of section 10.4 that begins with the sentence " If you are defining shared segments for Group3 printers...." should be deleted. While no malfunctions will occur as a result of following these directions, storage will become unavailable to every member of the GCS group, unnecessarily. This is usually not UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 015 OF 076 serious, but if a Group4 PDM is in the same group, it will not be able to support as many printers as it should. ************************************************************************ * SECTION 3. G E N E R A L I N F O R M A T I O N * ************************************************************************ THIS SECTION CONTAINS GENERAL INFORMATION, I.E. SYSGEN HINTS/TIPS. 37.99/04/23 "PN78572 added support for resident DBCS raster fonts. However, PSF/VM does not support referencing a double byte character set resident font by it's registered font ID (GRID). You can only reference it by it's coded font name." 36.98/11/13 The 4230, 4247, 64XX and 4224 printers have been enhanced to support the European currency symbol, the Euro. The Euro character has been added to the resident character sets and codepages have been added which contain the Euro codepoint. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 016 OF 076 PSF/VM supports the 4224 natively. PSF/VM supports the 4230 running in 4224 emulation mode only. PSF/VM supports the 4247 & 64XX printers running in 4234 emulation mode only. PSF/VM module APRFTBLB (Group 4) contains tables of character sets and codepages resident in the 4224 and 4234 type printers. PSF/VM APAR PQ21057 adds the new codepages to the resident font resource tables in APRFTBLB. If you have customized the APRFTBLB source code shipped with PSF/VM and have printers with the new resident codepages, you will either have to add the new codepages to your version of APRFTBLB or add your modifications to the version of APRFTBLB shipped with PQ21057. See the PSF/VM Systems Programmer's Guide UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 017 OF 076 Chapter 8 for more information on modifying, assembling and linkediting APRFTBLB into your Group 4 PDM. 35. 98/03/26 Message APRCCM742E the program that created the printfile or pagedef generated invalid data- unsuccessful skip to channel '12'. The input file contained TRC characters and had an invalid skip to channel 8, not 12. The ANZI channel codes are converted to MACHine channel codes on the VM spool. PSF cannot determine whether the codes were originally ANZI or MACH in all cases, so it treats them all as ANZI. The code for channel 8 (x'f8') is converted to x'c3'. This can be the MACH code for channel 8 or the ANZI code for channel 12. See the PSF/VM APPLICATION PROGRAMMING GUIDE chapter 5 table 4 for more information. 34. 98/03/26 Message APRABN559T PDM ABEND-SYSTEM ABEND X'01000' or X'02000'. This is not really a system abend but rather a user abend generated by the PDM due to the fact that it can't communicate with the printer. See the preceeding UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 018 OF 076 messages, E.G. APRIIO694S device not available, or APRERC696S permanent I/O error on device nnn. These are th key to the problem. 33. 98/01/20 APAR PQ03048 (Cut Sheet Emulation) changes the behaviour after message APRCCM753E. Prior to this apar, if the printfile called for a copygroup (medium map) that was not in the formdef, PSF/VM would issue message APRCCM753E and processing would continue using the first copygroup in the formdef. With PQ03048, APRCCM753e is issued and processing stops. 32. 96/04/18 The Application Programming Guide, page 160, specifies your virtual printer must be defined as a 3800 if you are using Table Reference Characters (TRC). This is true if you only have TRCs 0, 1, 2, or 3. A virtual 3800 will only honor TRCs 0, 1, 2 or 3. CP converts these to select translate table commands, of which there are only the four. If a customer has more than 4 TRCs, then they will need to use a UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 019 OF 076 non-3800 virtual printer such as a 1403 or VAFP. If the record length is greater than 133, they will need VAFP. Then, using the PSF command, you can specify CC TRC an they will be honored. An alternative which should also work is to run the job with the LINK option on the PSF command. 31. 96/02/22 Message msAPRERC696S A permanent I/O error on device 0560 was detected can be issued if the MIH option appears on the OPTION line in the CP directory for a channel attached printer. This is particularly evident in a d/t3900W1 or duplex printer. CP tries to handle missing interrupts by halting the IO and restarting it. Since the 'missing interrupt' is probably due to mormal operation of these printers, permanent IO errors result. The cure is to remove MIH from the CP user directory entry. 30. 94/12/01 In order to print on a printer on the same system as the user, the user' virual printer must be spooled to the system print queue. This is the default at logon time, but UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 020 OF 076 the user can issue any of the following comma to make sure: CP SPOOL 00E SYSTEM CP SPOOL 00E FOR * CP SPOOL 00E * PRT 29. 94/07/19 CMS 10, VMESA 2.1 appears to have substantially increased the amount of virtual storage used by CMS. As an example, virtual storage had to be increased to 6 meg in order to initialize a Group3 PDM. This may vary for each service machine. One of the symptoms is that the service machine will not complete initialization. 28. 93/09/02 Section of the PSF/VM 2.1.1 Installation PSP Bucket, U: PSFVM211 S: VM/211: PSF/VM 2.1.1 is NOT a seperate service stream (rollup of of product with service) from PSF/VM 2.1.0. They are the same service stream, and both use RETAIN release R210. The RETAIN release R211 for Component ID 568414101 was assigned to Resources with the base release of PSF/VM 2.1.0. The UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 021 OF 076 resources are the Page Definitions and Form Definitions supplied with PSF. PSF/VM 2.1.1 differs from PSF/VM 2.1.0 by including two new features, ACIF and AFP API (Component IDs 564806201 and 564806202). 27. 93/02/26 ON VM/SP5 and VM/SP6 systems, if the PSF command DCSS APRPSFC4 is defined in DMKSNT, but the segment isn't actually built, an error will occur upon execution of the PSF command because control will go to the defined location whether the code is loaded in the segment or not. If a PSF command DCSS is no longer desired, DMKSNT must be rebuilt removing the segment name to allow the PSF command to function correctly as a loadlib. 26. 92/10/08 4028 hang condition. If a hang is experienced with a D/T4028, have the CE open a hardware incident with the L2 hardware group and request the "BOULDER PATCH". One of the symptoms is that the job light is ON , yet no output. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 022 OF 076 25. 92/09/04 Microcode requirements for the control units listed below are as follows: A. IBM 3174 Establishment Controller with Configuration Support A require Release 5.2 with P6948 (or higher). Configuration Support B requires Release 2.0 with P6612 (or higher). B. IBM 3274 Control Unit Model 41A and 61C, with Configuration Support D, requires Release 65.1 (or higher). 24. 92/08/25 MSCSIGLB024E RPIGCS LOADLIB not found. This GCS error message is normal when RACF is not installed. 23. 92/07/27 II05202 (attached) is an information apar that discuss potential segment problems when defining a GCS SPACE. 22. 92/04/06 RC104 when building the DCSS for APRSFCM4 installing PSF 2.1.0. with VM/ESA. The failure is due to CMSVMLIB segmen UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 023 OF 076 being loaded at 8meg. The problem can be resolved before installing PSF by doing a 'SEGMENT RELEASE CMSVMLIB' or by coding 'SEGMENT RELEASE CMSLIB' into the I5684141 exec. 21. 92/03/03 PROCEDURE TO GO FROM NUCLEUS EXTENTION TO DCSS AFTER THE PRODUCT HAS BEEN INSTALLED: FIRST, PROPER VM DCSS DEFINITIONS MUST BE MADE AS AS DESCRIBED IN THE PSF/VM PROGRAM DIRECTORY. ALSO SEE WSC FLASH 9120 WHICH DESCRIBES SEGMENT PACKING FOR PSF/VM 2.1.0 INSTALL. THEN: 1) CREATE A BLANK MINIDISK 2) FROM PSFMAINT, INVOLK THE CORRECTIVE SERVICE EXEC FOR THE PSF COMPONENT TO BE CHANGED 3) FOLLOW THE STEPS OF THE EXEC UNTIL IT ASKS FOR THE ADDRESS OF THE DISK THAT CONTAINS THE PTF FIXES. 4) ENTER THE ADDRESS OF THE BLANK MINIDISK 5) LATER IN THE EXEC, IT ASKS IF THE COMPONENT IS TO BE GENERATED AS A DCSS. RESPOND 'YES'. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 024 OF 076 20. 92/02/17 IF A PROBLEM IS EXPERIENCED WHILE RUNNING THE PSF/VM 2.1.0 INSTALLATION EXEC 'I5684141 EXEC', GO TO THE TRACECMD: PROCEDURE AROUND LINE NUMBER 5910 AND REMOVE THE 'RETURN;' STATEMENT AFTER 'TRACECMD:'. THAT WILL ALLOW THE DEBUGGING PROCEDURE TO TRACE COMMANDS AS THEY ARE EXECUTED DURING THE BUILD PROCESS. THE INSTALLATION EXEC WILL STILL FUNCTION. HOWEVER, WHILE IT IS DOING WORK ALL THE COMMANDS THAT ARE ACTUALLY EXECUTED WILL BE DISPLAYED. THIS WILL HELP DIAGNOSE INSTALLATION PROBLEMS. THE SAME TRICK CAN BE USED WHEN APPLYING PUT SERVICE OR CORRECTIVE SERVICE USING THE PSF/VM SERVICE EXECS. FIRST, YOU MAY CHOOSE TO SAVE A COPY OF THE SERVICE EXEC BEFORE IT IS MODIFIED. THEN, TO FIND THE LOCATION OF THE 'RETURN;' STATEMENT TO DELETE, SEARCH FOR THE PROCEDURE NAME: 'TRACECMD:'. YOU SHOULD FIND A LINE WITH COMMENTS THAT LOOKS LIKE THIS: 'RETURN; /* REMOVE THIS RETURN IF COMMANDS ARE TO BE PRINTED */' DELETING THAT SINGLE LINE OF CODE WILL CAUSE THE TRACECMD: PROCEDURE CODE TO EXECUTE, PROVIDING A VISIBLE TRACE OF COMMANDS EXECUTED. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 025 OF 076 19. 92/01/31 BEFORE SELECTING IDENTIFIER 'F' (FONTS) FROM I5684141 MENU, ENSURE THE FONTS PRODUCT TAPE IS LOADED AND THE FIRST TWO FILES ARE LOADED FROM THE FONTS TAPE WHICH WILL CORRECTLY POSITION THE TAPE. 18. 92/01/31 AFTER THE I5684141 EXEC AND MEMO HAVE BEEN LOADED FROM THE INSTALL TAPE ONCE, YOU MUST ENSURE THAT THE TAPE IS POSITIONED AT TAPE FILE 3 BEFORE INVOKING THE I5684141 EXEC AGAIN TO INSTALL ADDITIONAL FEATURES. 17. 92/01/23 IF A D/T3820 OR D/T3812 PDM TERMINATES WITH MSCSIABD230E "COMMAND EXEC FAILED" ABEND0C2, THE PDM ID IS NOT AUTHORIZED TO GCS. THE ABEND0C2 SIGNIFIES THE PDM IS INSTALLED AS A SHARED SEGMENT. IF THE D/T3820 OR D/T3812 TERMINATES WITH MSAPRABN559T PDM ABEND- SYSTEM COMPLETION CODE X'B0A', MSCSIABC230E "COMMAND EXEC FAILED" SYSTEM ABEND B0A-0000, THE PDM ID IS NOT AUTHORIZED TO GCS. THE B0A ABEND MEANS THE PDM IS INSTALLED AS A MODULE. THE GCS GROUP EXEC AND ASSOCIATED PROCEDURES NEED TO BE RUN UNTIL UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 026 OF 076 AUTHORIZATION IS SUCCESSFUL AND A CHECK SHOULD BE DONE TO ENSURE AUTHEXIT = YES ON AN APPL STATEMENT WHICH DEFINES SOME OF THE COMMUNICATIONS CAPABILITIES OF THE APPLICATION PROGRAM. After making these changes, GCS must be regen'd. 16. 91/11/26 THE SAMPLE VM DIRECTORY ENTRIES IN THE PROGRAM DIRECTORY INCLUDE OPTION PARAMETERS OF BMX AND ECMODE. THESE TWO PARAMETERS ARE NOT VALID FOR THE VM/XA OR VM/ESA (WITH THE ESA FEATURE) ENVIRONMENT. DIRMAINT WILL ISSUE A MESSAGE STATING THAT THEY ARE INVALID PARMS FOR THE OPTION STATEMENT. THE MIXED OPTION OF THE DIRECTXA COMMAND WILL IGNORE MOST VM/SP OR VM/SP HPO SOURCE STATEMENTS THAT IT DOESN'T SUPPORT AND WILL SEND A WARNING, BUT WILL CONTINUE TO CREATE THE UPDATED DIRECTORY. SEE THE VM/XA OR VM/ESA (WITH ESA FEATURE) PLANNING AND ADMINISTRATION MANUAL FOR INFORMATION ON THE DIRECTORY STATEMENTS AND THE DIRECTXA COMMAND. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 027 OF 076 15. 91/11/21 IF THE DATA STREAMING FEATURE IS ENABLED ON THE PRINTER, ENSURE THAT THE UCW IS ALSO SET FOR THE DATA STREAMING FEATURE. IMPROPER CONFIGURATION OF THE DATA STREAMING FEATURE CAN CAUSE MSAPRS1G000E OR OTHER MESSAGES INDICATING DATA IN AN INPUT RECORD OR RESOURCE IS INVALID. THESE MESSAGES ARE INVALIDLY ISSUED. 14. 91/09/24 CUSTOMERS INSTALLING GROUP4 PDM NEED TO OBTAIN DOC APAR PN05808. USERS AFFECTED: ALL PSF/VM 2.1.0 INSTALLATIONS USING THE GROUP4 PDM. PROBLEM DESCRIPTION: AFTER INSTALLING PSF/VM AND INVOKING THE IVP EXEC (V5684141), THE IVP DID NOT PRINT ON THE GROUP4 PRINTER. RECOMMENDATION: MODIFY THE FORM PDM FILE OR CREATE UNIQUE FORM TASKPRTID FILES TO MATCH INSTALLATION REQUIREMENTS SEE PN05808 (ATTACHED). 13. 91/08/07 THE DMKSNT SFCM SAMPLE FILE SHIPPED WITH PSF/VM 2.1.0 UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 028 OF 076 IS INCORRECT. A CORRECT DMKSNT SFCM SAMPLE FILE IS SHOWN BELOW. THE SAMPLE BELOW MATCHES THE SAMPLE DOCUMENTED IN THE PROGRAM DIRECTORY (G5443683-00) ON PAGE 39, WHICH IS CORRECT: ******************************************************** * PSF/VM (PROGRAM NO. 5684-141 PRINT SERVICES FACILITY * * FOR VM) APRSFCM4 DISCONTIGUOUS SAVE SEGMENT - DCSS * * FOR PSF/SFCM * * HEX LOAD ADDRESS FOR SEGMENT 128 = 8000000 * * NUMBER OF PAGES = 113 ( 112 + 1 FOR CP ) * ******************************************************** APRSFCM4 NAMESYS SYSNAME=APRSFCM4, SYSVOL=XXXXXX, SYSSTRT=(098,010), SYSPGNM=(2048-2159), SYSPGCT=112, SYSHRSG=(128-134), SYSSIZE=2048K, UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 029 OF 076 SYSCYL= VSYSRES=, VSYSADR=IGNORE 12. 91/07/29 THE CORRECTIVE SERVICE EXECS FOR PSF/VM ARE NAMED AS FOLLOWS: PTFSERVP FOR THE PSF COMMAND PTFSERVB FOR PRINT SERVICES (SFCM) PTFSERVA FOR THE GROUP3 PDM ATTACH SUPPORT PTFSERVL FOR THE GROUP4 PDM ATTACH SUPPORT PTFSERVS FOR THE 3800 PDM ATTACH SUPPORT PTFSERVV FOR THE 3820 PDM ATTACH SUPPORT 11. 91/07/17 THE RELEASE LEVELS USED FOR PSF/VM 2.1.0 APARS AND PTFS ARE AS FOLLOWS: 2B6 - PSF COMMAND 210 - PSF PRING SERVICES (SPOOL FILE CONVERSION MACHINE-SFCM) 2B7 - 3800 PRINTER DRIVER MACHINE (PDM) UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 030 OF 076 2B8 - 3820 PDM 2B9 - GROUP3 PDM 211 - RESOURCES 2BB - GROUP4 PDM 10. 91/05/30 THE CP MIH/MITIME VALUE FOR A GRP3 PRINTER ATTACHED TO PSF SHOULD NEVER BE LESS THAN THE PSF MITIME VALUE FOR THE PRINTER. IF A NON-ZERO MITIME VALUE IS SPECIFIED IN THE PSF GRP3 OPTIONS PDM FILE, THEN THE CP MIH/MITIME SHOULD BE TURNED OFF FOR THE PDM VIRTUAL MACHINE OR FOR THAT PRINTER, OR THE CP MITIME VALUE FOR THE PRINTER SHOULD BE SET GREATER THAN THE PSF MITIME VALUE. 9. 91/05/30 IF A D/T3800 IS GENNED WITH DEVTYPE AFP1 RUNNING PSF WITH VM/ESA, THE 3800 PDM WILL NOT INITIALIZE AND NO MESSAGE IS ISSUED. ENSURE THAT THE D/T3800 IS GENNED WITH DEVTYPE OF 3800. 8. 91/05/24 CODE PAGE T1D0BASE IS MAPPED TO 4028 PRINTER RESIDENT CODE UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 031 OF 076 PAGE X'3EA' (1002) IN THE APRRSFTB ASSEMBLE FONT RESOURCE TABLE SAMPLE PROVIDED WITH PSF/VM 2.1.0. THERE ARE SOME CODE POINT DIFFERENCES BETWEEN HOST CODE PAGE T1D0BASE AND CODE PAGE 1002. CODE PAGE T1D0BASE IS A SUPERSET OF CODE PAGE 1002. THAT IS, IT CONTAINS A FEW CODE POINTS THAT 1002 DOES NOT. HOST CODE PAGE 1002 (T1001002) AND PRINTER RESIDENT CODE PAGE 1002 ARE EQUIVALENT. IF AN INSTALLATION PLANS TO USE THE ADDITIONAL CODE POINTS DEFINED IN T1D0BASE BUT NOT DEFINED IN T1001002, THEN THE T1D0BASE ENTRY IN THE APRRSFTB TABLE SHOULD BE COMMENTED OUT OR DELETED. THIS WILL CAUSE PSF/VM TO DOWNLOAD THE FONT USING THE HOST VERSION OF T1D0BASE INSTEAD OF ACTIVATING THE PRINTER RESIDENT VERSION. IN MOST CASES, THIS CHANGE IS RECOMMENDED SO THAT ALL POSSIBLE PRINTED OUTPUT IS CORRECT. 7. 91/05/23 PLEASE REFER TO WSC FLASH 9120 PSF/VM 2.1.0 MANUAL INSTALL PROCEDURES FOR INFORMATION ABOUT PRODUCT INSTALLATION LOGIC. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 032 OF 076 6. 91/05/16 FOR CUSTOMERS WITH GRP4 PRINTERS ATTACHED TO PSF/VM 1.3.0 OR PSF/VM 2.1.0 IN 3270 DSC (NON-SNA) MODE, THE FOLLOWING CONTROLLER MICROCODE LEVELS ARE REQUIRED: 3174 SUBSYSTEM CONTROL UNIT MICROCODE LEVEL A5.0 OR HIGHER 3274 CONTROL UNIT MICROCODE LEVEL D65.1 OR HIGHER 9370 WORKSTATION ADAPTER (FEATURE 6020) MICROCODE LEVEL EC A866889 OR HIGHER 5. 91/05/05 WHEN PLANNING AND INSTALLING PSF/VM 2.1.0, OBTAIN A COPY OF THE WASHINGTON SYSTEM CENTER (WSC) FLASH 9117 ENTITLED, 'PSF/VM 2.1.0 AND FONTS'. CONTACT YOUR SE FOR A COPY. 4. 91/04/18 OBTAIN A COPY OF PSP BUCKET UPGRADE: AFPFONT, SUBSET: PSF210, FOR FONT PROBLEMS. 3. 91/04/18 ON A VM/XA OR VM/ESA SYSTEM, SHARED SEGMENT PACKING SHOULD BE USED. IF IT IS NOT USED, IT MAY BE NECESSARY TO DEFINE UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 033 OF 076 A FULL 1 MEG SEGMENT FOR EACH DCSS. THIS MAY BE A MEMORY MANAGEMENT PROBLEM WITH ONE SYMPTOM BEING MSCSIABD230E ABEND 0C1, ALTHOUGH THERE MAY BE OTHERS. FOR INFO ON SHARED SEGMENT PACKING, SEE GUIDE TO SAVED SEGMENTS (SC23-0457). 2. 91/04/18 ABENDS 806-0004 ON GROUP 4 PDMS WILL OCCUR IF THE APRGRP44 DCSS IS NOT DEFINED TO GCS. 1. 91/04/18 THE CMS PTF PREREQUISITES LISTED IN THE 'INSTALLATION REQUIREMENTS AND CONSIDERATIONS, SECTION 5.1.2, PAGE 18, OF THE PSF/VM 2.1.0 PROGRAM DIRECTORY ARE REQUIRED. NOTE THAT CMS PTFS UV51488 AND UV46124 ARE BOTH REQUIRED FOR VM/SP5 AND VM/SP HPO5 SYSTEMS. A SYMPTOM INDICATING THAT THE CMS PTFS HAVE NOT BEEN APPLIED IS: MSDMSITP141T OPERATION EXCEPTION OCCURRED AT LOCATION X'00006' IN ROUTINE APRSFCMC. THE D/T3800 PDM AND GROUP3 PDM WILL ALSO ABEND. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 034 OF 076 ANOTHER SYMPTOM THAT THE CMS PTFS ARE NOT APPLIED IS: MSAPRPSF933S "I/O ERROR WRITING TO SPOOL: FILE WAS NOT SPOOLED". ************************************************************************ * SECTION 4. S E R V I C E R E C O M M E N D A T I O N S * ************************************************************************ 19 97/12/10 PROBLEM: (PQ09099) PRINT JOB HANGS USING CUT SHEET EMULATION OR N-UP. USERS AFFECTED: PSF/VM 210 customer's using N-UP or Cut Sheet Emulation (CSE) functions. RECOMMENDATION: INSTALL UQ12280 ON VOLID 1000 18 97/12/05 PROBLEM: (PQ06815) SLOW PERFORMANCE, BLANK PAGES, WRONG/MISSING FONTS, MISSING OVERLAY USERS AFFECTED: PSF/VM 2.1.0 and PSF/VM 2.1.1 users running Group 3 or Group 4 printers and experiencing start/stop behavior UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 035 OF 076 on the printer while printing. RECOMMENDATION: INSTALL UQ08286 ON VOLID 1000 17 97/12/05 PROBLEM: (PQ06815) SLOW PERFORMANCE, BLANK PAGES, WRONG/MISSING FONTS, MISSING OVERLAY USERS AFFECTED: PSF/VM 2.1.0 and PSF/VM 2.1.1 users running Group 3 or Group 4 printers and experiencing start/stop behavior on the printer while printing. RECOMMENDATION: INSTALL UQ08287 ON VOLID 1000 16 93/08/10 PROBLEM: (PN43123) PTFSERVA PTFSERVL PTFSERVV RC=4 FROM THE LOAD COMMAND WHEN CREATING DCSS. 93/07/02 PTF PECHANGE USERS AFFECTED: PSF/VM users using the PTFSERVL, PTFSERVA or PTFSERVV execs to buildPDM programs in shared segments ( DCSSs ). UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 036 OF 076 RECOMMENDATION: INSTALL UN47233 ON VOLID 9401 15 93/08/10 PROBLEM: (PN43123) PTFSERVA PTFSERVL PTFSERVV RC=4 FROM THE LOAD COMMAND WHEN CREATING DCSS. 93/07/02 PTF PECHANGE USERS AFFECTED: PSF/VM users using the PTFSERVL, PTFSERVA or PTFSERVV execs to buildPDM programs in shared segments ( DCSSs ). RECOMMENDATION: INSTALL UN47232 ON VOLID 9401 14 93/08/10 PROBLEM: (PN43123) PTFSERVA PTFSERVL PTFSERVV RC=4 FROM THE LOAD COMMAND WHEN CREATING DCSS. 93/07/02 PTF PECHANGE USERS AFFECTED: PSF/VM users using the PTFSERVL, PTFSERVA or PTFSERVV execs to buildPDM programs in shared segments ( UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 037 OF 076 DCSSs ). RECOMMENDATION: INSTALL UN47231 ON VOLID 9401 13 93/08/10 PROBLEM: (PN43123) PTFSERVA PTFSERVL PTFSERVV RC=4 FROM THE LOAD COMMAND WHEN CREATING DCSS. 93/07/02 PTF PECHANGE USERS AFFECTED: PSF/VM users using the PTFSERVL, PTFSERVA or PTFSERVV execs to buildPDM programs in shared segments ( DCSSs ). RECOMMENDATION: INSTALL UN47230 ON VOLID 9401 12 93/08/10 PROBLEM: (PN43123) PTFSERVA PTFSERVL PTFSERVV RC=4 FROM THE LOAD COMMAND WHEN CREATING DCSS. 93/07/02 PTF PECHANGE USERS AFFECTED: PSF/VM users using the PTFSERVL, PTFSERVA or PTFSERVV execs to UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 038 OF 076 buildPDM programs in shared segments ( DCSSs ). RECOMMENDATION: INSTALL UN47229 ON VOLID 9401 11 93/08/10 PROBLEM: (PN43123) PTFSERVA PTFSERVL PTFSERVV RC=4 FROM THE LOAD COMMAND WHEN CREATING DCSS. 93/07/02 PTF PECHANGE USERS AFFECTED: PSF/VM users using the PTFSERVL, PTFSERVA or PTFSERVV execs to buildPDM programs in shared segments ( DCSSs ). RECOMMENDATION: INSTALL UN47228 ON VOLID 9401 10 93/08/06 PROBLEM: (PN38057) ADD SUPPORT FOR ACIF AND AFP API TO INSTALLATION AND CORRECTIVE SERVICE EXECS USERS AFFECTED: PSF/VM 2.1.1 users RECOMMENDATION: INSTALL UN44283 ON VOLID 9401 UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 039 OF 076 9 93/08/06 PROBLEM: (PN38057) ADD SUPPORT FOR ACIF AND AFP API TO INSTALLATION AND CORRECTIVE SERVICE EXECS USERS AFFECTED: PSF/VM 2.1.1 users RECOMMENDATION: INSTALL UN44282 ON VOLID 9401 8 93/08/06 PROBLEM: (PN38057) ADD SUPPORT FOR ACIF AND AFP API TO INSTALLATION AND CORRECTIVE SERVICE EXECS USERS AFFECTED: PSF/VM 2.1.1 users RECOMMENDATION: INSTALL UN44281 ON VOLID 9401 7 93/08/06 PROBLEM: (PN38057) ADD SUPPORT FOR ACIF AND AFP API TO INSTALLATION AND CORRECTIVE SERVICE EXECS USERS AFFECTED: PSF/VM 2.1.1 users RECOMMENDATION: INSTALL UN44280 ON VOLID 9401 UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 040 OF 076 6 93/08/06 PROBLEM: (PN38057) ADD SUPPORT FOR ACIF AND AFP API TO INSTALLATION AND CORRECTIVE SERVICE EXECS USERS AFFECTED: PSF/VM 2.1.1 users RECOMMENDATION: INSTALL UN44279 ON VOLID 9401 5 93/08/06 PROBLEM: (PN38057) ADD SUPPORT FOR ACIF AND AFP API TO INSTALLATION AND CORRECTIVE SERVICE EXECS USERS AFFECTED: PSF/VM 2.1.1 users RECOMMENDATION: INSTALL UN44278 ON VOLID 9305 4 92/03/16 PROBLEM: (PN08536) SFCM PERIODICALLY NEEDS AUDIT ON TO CONVERT FILES. END OF ABSTRACT USERS AFFECTED: ALL PSF/VM 2.1.0 INSTALLATIONS WITH AN SFCM DRIVING MORE THAN 1 PDM OR GROUP4 PRINTER TASK PROGRAM. RECOMMENDATION: INSTALL UN09958 ON VOLID 9201 UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 041 OF 076 3 91/11/26 PROBLEM: (PL83703) PRINTING A GERMAN CHARACTER CONSISTING OF AN O WITH TWO DOTS ABOVE IT GIVES INCORRECT OUTPUT USERS AFFECTED: ALL PSF/VM 2.1.0 CUSTOMERS USING THE GROUP3 PDM AND CHANNEL ATTACHED GROUP3 PRINTERS. RECOMMENDATION: INSTALL UL97732 ON VOLID 9105 2. 91/11/13 ITEM DELETED 91/11/14 1. 91/11/13 ITEM DELETED 91/11/14 ************************************************************************ * SECTION 5. C R O S S P R O D U C T D E P E N D E N C I E S * ************************************************************************ THIS SECTION CONTAINS INFORMATION THAT IS DEPENDENT UPON ANOTHER PRODUCT OTHER THAN THIS SUBSET ID. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 042 OF 076 4. 92/09/28 INTERDEPENDENT PRODUCT: VM CP PROBLEM: PSF/VM customers on VM/SP5, VM/HPO5, VM/SP6 and VM/HPO6 systems may experience symptom: MSAPRSSE298T "A PSF LOGIC ERROR INVOLVING APROPRC WAS DETECTED, RC(1106)" A CP PE APAR resolves the problem, VM38497 USERS AFFECTED: All with VM35694 using *SPL RECOMMENDATION: Install PTF UV47314 (RD75) on volid 9002 Install PTF UV47312 (RA50) on volid 9002 Install PTF UV47315 (RD76) on volid 9002 Install PTF UV47313 (RA60) on volid 9002 3. 92/09/18 INTERDEPENDENT PRODUCT: VM/ESA CMS R111 PROBLEM: If attempting to print using TRCs from a VM/ESA 1.1.1 CMS print file submittor, the output may print using only the first font. That is, TRCs 0,1,2 and 3 all print with the TRC 0 font. VM51332 fixes a problem in CMS (DMSPIO) which caused this problem. UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 043 OF 076 USERS AFFECTED: ALL RECOMMENDATION: INSTALL PTF UM21085 ON VOLID 1000 2. 92/08/07 INTERDEPENDENT PRODUCT: DW/370 PROBLEM: APRLPSFC fails when invoked from DW/370 running above the line. ABENDU1000 is received. USERS AFFECTED: Applications that incorporate APRLSPFC above 16M line. RECOMMENDATION: INSTALL PTF UN03218 ON VOLID 9201 1. 91/09/06 INTERDEPENDENT PRODUCT: PSF/VM & RACF 1.9 USERS AFFECTED: USERS OF PSF/VM AND RACF 1.9 PROBLEM: WHEN OPERATING PSF/VM WHERE RACF 1.9 IS ON THE SAME SYSTEM, OR ON A SYSTEM WHICH SHARES DASD WITH A SYSTEM WHERE RACF 1.9 IS INSTALLED, PLEASE REVIEW AND APPLY PSF/VM 1.3.0 APAR PL85977 OR PSF/VM 2.1.0 APAR PN00203. THESE APARS AFFECT THE CMS COMPONENTS OF PSF/VM ONLY (SFCM, 3800 PDM AND GROUP3 NON-SNA PDM). THE GCS COMPONENTS OF PSF/VM (GROUP 4 PDM, 3820 PDM OR GROUP 3 SNA PDM SHOULD NOT ACCESS UPGRADE: PSFVM210 SUBSET: VM/210 INTRODUCTORY TEXT PG 044 OF 076 A DISK CONTAINING RPIUGCS LOADLIB. FOR FURTHER INFORMATION REGARDING VM US DEPARTMENT OF DEFENSE (DOD) SECURITY SUPPORT, SEE ANNOUNCEMENT LETTER 391-029 ENTITLED 'VM US DOD SECURITY SUPPORT TO BE CONSOLIDATED ON VM/ESA 1.1'. RECOMMENDATION: INSTALL PSF/VM APAR PL85977 FOR PSF130 AND PN00203 FOR PSF21. ************************************************************************ * I N F O R M A T I O N A L / D O C U M E N T A T I O N * * APARS FOLLOW (IF ANY) * ************************************************************************ UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 045 OF 076 APAR NUMBER = II05202 LAST UPDATE = 93/04/23 PTF IN ERROR = PIN = YES CURRENT APAR STATUS = CLOSED CLOSING CODE = CAN ORIGINAL APAR NUMBER = SECURITY/INTEGRITY = NO SERVICE NUMBER = 5NFO000 000 REPORTED COMPONENT = INFODSLIB R001 DS LIB INFO ITE FIXED COMPONENT = FAILING MODULE = PROBLEM ABSTRACT: GENERAL INFORMATION REGARDING GCS AND ASSOCIATED ERRORS REPORTED SCP RELEASE: 000 ERROR DESCRIPTION: This APAR describes some common problems that may be encountered when in stalling shared segments in the GCS environment. . Part A : VM/SP Environment VMSPGCS . UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 046 OF 076 1. When installing GCS in the VM/SP environment, you must ensure that the GCS shared segment does not overlap with any of the other segments listed in the GCS GROUP file. (The location of these segments is defined to CP in your DMKSNT ASSEMBLE file.) . 2. The two SLC statements in your GCSLOAD exec must match the starting and ending addresses of your GCS segment, as defined to CP. If these do not match, GCS may very likely fail to complete initialization, and you may see the following message: CP ENTERED; PROGRAM INTERRUPT LOOP You may also identify this problem by looking in your GCSNUC MAP for the load addresses of CSIALP and CSIZET and comparing them to the starting and ending addresses, respectively, of the GCS segment in CP's definition. Note: The SLC statements are actually file identifiers. For each SLC statemtent in the GCSLOAD exec, you must have a corresponding "SLC Ln00000" file, containing the UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 047 OF 076 correct address, in your access order. Note that because of build restrictions GCS cannot be loaded up to the 16meg line. GCS build processing does not recognize an SLC 000000 or SLC 1000000 statement. . 3. The GCS GROUP file should only include segments that will be required by ALL of the machines in the group. DO NOT include GCS, CMS (CMS and GCS are mutually exclusive), CMSBAM or CMSVSAM in this list. . 4. (This item is only applicable if you are installing NetView or will be using any other application that opens DOS ACB's.) . GCS will only load CMSVSAM and CMSBAM when an application tries to open a DOS ACB, so when GCS initializes, if the addresses of one of these segments is within the virtual machine (e.g., the NETVIEW machine is defined as 12 meg, and the DOS segments are defined from 10 to 12 meg.), GCS will not "reserve" storage for them, and will consider that part of storage private. This can UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 048 OF 076 cause many errors to occur, some of which include, but are not limited to: - The DOS segment will overlay existing private storage areas when it is loaded in. - A program check type '04' may occur when GCS, thinking it is using private storage, attempts to write on top of the DOS segment after it is loaded in. - The DOS segment may overlap, or be overlapped by another shared segment (see item "1" above). . For these reasons, it is recommended that you define your DOS segments outside the virtual machine size of the virtual machines that will use them. . 5. After building your GCS segment and IPL-ing the reader, you will have a GCS nucleus map on your reader. You should receive this file to a disk and examine it for possible errors. In particular, be wary of UNDEFINED and UNRESOLVED REFERENCE statements at the bottom of the map. If you find any, it is UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 049 OF 076 likely that you have some kind of maintenance mismatch, probably between your GCS code and your GCSLOAD exec. . Part B : VM/XA Environment VMXAGCS . 1. All of the rules concerning GCS described for the VM/SP environment are applicable in the VM/XA environment. In the VM/XA environment, however, shared segments are implemented somewhat differently, and require some additional consider- ations. Please refer to the "Guide To Shared Segments" (SC23-0457-0) for a complete description of these differences. A key difference, worth noting here, is that the definition of a segment has changed from VM/SP, which defined a segment boundary as every 16 pages, or x'1000' bytes. With VM/XA, segments are now 1 megabyte in length, and must be defined accordingly for the entire megabyte. (Failure to do so may result in ABEND0C4 and ABEND0C5 errors.) . 2. In order to conserve storage, it is common to include UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 050 OF 076 related smaller segments together in the same "space", and load them at the same time with one command. It is, therefore, important to consider each individual member of a segment space when making considerations for overlapping segments. Like the VM/SP environment, this space is NOT to be included in the GCS GROUP file's list of segments to be loaded at initialization time. . 3. Because segments must span an entire megabyte in VM/XA, you may encounter storage constraints if you have 3 or 4 segments included in the GCS GROUP file. One way to help alleviate this problem is to define a GCS space (not just a segment) that includes the segments which are to be loaded at initialization time. This will then permit you to define any of the constituent segments for less than a megabyte, if so desired. . 3. Rules for defining a GCS space: a. The first segment must start on the megabyte boundary. UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 051 OF 076 b. There can be no gaps between the segments. . c. The last segment must end on a megabyte boundary. d. The space may only include segments listed in the GCS GROUP file. e. The name of the space cannot be the same as any of its constituent members. f. If any of the segments included in the space is restricted, then the entire space, and, therefore, each segment in the space, is considered restricted. g. A NAMESAVE statement must be included in the user directory entry of every machine that will IPL GCS (or any other restricted segment). The NAMESAVE statement must have the name of the space, however, and not each individual segment, in order to work. h. If you define a GCS space, each segment in that space must have been previously saved. If all segments in the space are not saved, CP will not load the space at all. This could result in many different kinds of errors, including ABEND0C1, ABEND0C4, and ABEND0C5. UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 052 OF 076 A good indication of this error is that a dump taken as a result of this error will contain all zeroes at the location of the space. (If the space is outside the virtual machine, the space will not be accessible. . Part C : VM/ESA Environment VMESAGCS . 1. All of the rules concerning GCS described for the VM/SP and VM/XA environments are applicable in the VM/ESA environment, with the following exception. In the VM/ESA environment, you must specify where the DOS segments are loaded and which virtual machines will be using those segments. (These user ID's are named in the GROUP panel entitled "USERIDS REQUIRING RESERVED STORAGE FOR VSAM".) This allows you to IPL GCS in a machine that has the DOS segments contained within its storage without any of the aforementioned problems. Note: If you edit or create the GCS ASSEMBLE (GCS GROUP) file manually, you may encounter various assembly and/or VMFBLD UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 053 OF 076 errors. One of the more common errors is the appearance of UNRESOLVED REFERENCEs to CONUSED and CONUSRS. Such errors can usually be resolved by running the GROUP exec instead of editing the file manually. . Additional keywords: PROG001 PRG001 PROGRAM EXCEPTION 001 ABEND0C1 ABENDS0C1 PROG004 PRG004 PROGRAM EXCEPTION 004 ABEND0C4 ABENDS0C4 PROG005 PRG005 PROGRAM EXCEPTION 005 ABEND0C5 ABENDS0C5 PROG 1 4 5 PROG1 PROG4 PROG5 MSHCPGIR453W 5749CSI00 R475 RD74 R476 RD76 566430804 R120 R121 568411210 568411211 R110 R111 R120 TEMPORARY FIX: PROBLEM SUMMARY: PROBLEM CONCLUSION: MODULES/MACROS: SRLS: UPGRADE: PSFVM210 SUBSET: VM/210 APAR II05202 PG 054 OF 076 CIRCUMVENTION: APPLICABLE COMPONENT LEVEL/SU: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 055 OF 076 APAR NUMBER = PN05808 LAST UPDATE = 91/09/12 PTF IN ERROR = PIN = YES CURRENT APAR STATUS = CLOSED CLOSING CODE = DOC ORIGINAL APAR NUMBER = SECURITY/INTEGRITY = NO SERVICE NUMBER = 0462041 REPORTED COMPONENT = 568414101 R210 PSF/VM V2 R1.0 FIXED COMPONENT = FAILING MODULE = PROBLEM ABSTRACT: INSTALLING D/T4028 IVP NO PRINT OUT NO ERROR MESSAGE, V5684141 PSF/VM 2.1.0 GROUP4. REPORTED SCP RELEASE: 210 ERROR DESCRIPTION: INSTALLING D/T4028 IVP NO PRINT OUT NO ERROR MESSAGE, V5684141 PSF/VM 2.1.0 GROUP4. THE SFCM DOES NOT CONVERT THE FILE AND THE PRINTER IS IDLE. ERROR IN THE PSF/VM SYSTEM PROGRAMMING GUIDE S5443680-00 CHAPTER 5 PAGE 189 'FIGURE 34 SAMPLE GROUP4 FORM PDM FILE' TEMPORARY FIX: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 056 OF 076 PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: ALL PSF/VM 2.1.0 INSTALLATIONS USING THE * * GROUP4 PDM * **************************************************************** * PROBLEM DESCRIPTION: AFTER INSTALLING THE PSF/VM PRODUCT AND * * INVOKING THE INSTALLATION VERIFICATION * * EXEC (V5684141), THE IVP DID NOT PRINT * * ON THE GROUP4 PRINTER. THE SFCM DID * * NOT CONVERT THE FILE. THE FORM PDM * * FILE PROVIDED AS A SAMPLE WAS USED * * UNMODIFIED. THE FORM NAME USED BY THE * * CUSTOMER TO SUBMIT THE PRINT FILE WAS * * 'STANDARD'. FORM 'STANDARD' WAS NOT * * DEFINED IN THE FORM PDM FILE (OR IN A * * UNIQUE FORM TASKPRTID FILE). * **************************************************************** * RECOMMENDATION: UPDATE THE PSF/VM SYSTEM PROGRAMMING GUIDE * * (S5443680-00) PER THIS APAR. MODIFY THE * UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 057 OF 076 * FORM PDM FILE OR CREATE UNIQUE FORM * * TASKPRTID FILES TO MATCH INSTALLATION * * REQUIREMENTS. IF NO CUSTOMIZATION IS * * REQUIRED AND FORM 'STANDARD' IS USED, THEN * * ADD THE LINE 'STANDARD SEP' TO THE FORM PDM * * FILE. * **************************************************************** CHANGE FIGURE 34 'SAMPLE GROUP4 FORM PDM FILE' ON PAGE 189 OF THE PSF/VM SYSTEM PROGRAMMING GUIDE S5443680-00 TO THE FOLLOWING: * SAMPLE FORM PDM FILE FOR A GROUP4 PRINTER * * SEPARATOR PAGES SPECIFIED: STANDARD SEP * SEPARATOR PAGES NOT SPECIFIED: FORMSEP NOSEP * HEADER ONLY: FORMHDR H UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 058 OF 076 PROBLEM CONCLUSION: THE PSF/VM SYSTEM PROGRAMMING GUIDE HAS BEEN MODIFIED TO CORRECT THE PROBLEM. THE SAMPLE FORM PDM FILE SHIPPED WITH THE PSF/VM 2.1.0 GROUP4 PDM (FORM PDMGRP4) SHOULD EITHER BE CHANGED TO MATCH THE ABOVE EXAMPLE OR CUSTOMIZED TO MATCH THE FORM NAMES TO BE USED IN THE INSTALLATION. MODULES/MACROS: SRLS: S544368000 CIRCUMVENTION: APPLICABLE COMPONENT LEVEL/SU: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 059 OF 076 APAR NUMBER = PN05808 LAST UPDATE = 91/09/12 PTF IN ERROR = PIN = YES CURRENT APAR STATUS = CLOSED CLOSING CODE = DOC ORIGINAL APAR NUMBER = SECURITY/INTEGRITY = NO SERVICE NUMBER = 0462041 REPORTED COMPONENT = 568414101 R210 PSF/VM V2 R1.0 FIXED COMPONENT = FAILING MODULE = PROBLEM ABSTRACT: INSTALLING D/T4028 IVP NO PRINT OUT NO ERROR MESSAGE, V5684141 PSF/VM 2.1.0 GROUP4. REPORTED SCP RELEASE: 210 ERROR DESCRIPTION: INSTALLING D/T4028 IVP NO PRINT OUT NO ERROR MESSAGE, V5684141 PSF/VM 2.1.0 GROUP4. THE SFCM DOES NOT CONVERT THE FILE AND THE PRINTER IS IDLE. ERROR IN THE PSF/VM SYSTEM PROGRAMMING GUIDE S5443680-00 CHAPTER 5 PAGE 189 'FIGURE 34 SAMPLE GROUP4 FORM PDM FILE' TEMPORARY FIX: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 060 OF 076 PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: ALL PSF/VM 2.1.0 INSTALLATIONS USING THE * * GROUP4 PDM * **************************************************************** * PROBLEM DESCRIPTION: AFTER INSTALLING THE PSF/VM PRODUCT AND * * INVOKING THE INSTALLATION VERIFICATION * * EXEC (V5684141), THE IVP DID NOT PRINT * * ON THE GROUP4 PRINTER. THE SFCM DID * * NOT CONVERT THE FILE. THE FORM PDM * * FILE PROVIDED AS A SAMPLE WAS USED * * UNMODIFIED. THE FORM NAME USED BY THE * * CUSTOMER TO SUBMIT THE PRINT FILE WAS * * 'STANDARD'. FORM 'STANDARD' WAS NOT * * DEFINED IN THE FORM PDM FILE (OR IN A * * UNIQUE FORM TASKPRTID FILE). * **************************************************************** * RECOMMENDATION: UPDATE THE PSF/VM SYSTEM PROGRAMMING GUIDE * * (S5443680-00) PER THIS APAR. MODIFY THE * UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 061 OF 076 * FORM PDM FILE OR CREATE UNIQUE FORM * * TASKPRTID FILES TO MATCH INSTALLATION * * REQUIREMENTS. IF NO CUSTOMIZATION IS * * REQUIRED AND FORM 'STANDARD' IS USED, THEN * * ADD THE LINE 'STANDARD SEP' TO THE FORM PDM * * FILE. * **************************************************************** CHANGE FIGURE 34 'SAMPLE GROUP4 FORM PDM FILE' ON PAGE 189 OF THE PSF/VM SYSTEM PROGRAMMING GUIDE S5443680-00 TO THE FOLLOWING: * SAMPLE FORM PDM FILE FOR A GROUP4 PRINTER * * SEPARATOR PAGES SPECIFIED: STANDARD SEP * SEPARATOR PAGES NOT SPECIFIED: FORMSEP NOSEP * HEADER ONLY: FORMHDR H UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN05808 PG 062 OF 076 PROBLEM CONCLUSION: THE PSF/VM SYSTEM PROGRAMMING GUIDE HAS BEEN MODIFIED TO CORRECT THE PROBLEM. THE SAMPLE FORM PDM FILE SHIPPED WITH THE PSF/VM 2.1.0 GROUP4 PDM (FORM PDMGRP4) SHOULD EITHER BE CHANGED TO MATCH THE ABOVE EXAMPLE OR CUSTOMIZED TO MATCH THE FORM NAMES TO BE USED IN THE INSTALLATION. MODULES/MACROS: SRLS: S544368000 CIRCUMVENTION: APPLICABLE COMPONENT LEVEL/SU: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN18912 PG 063 OF 076 APAR NUMBER = PN18912 LAST UPDATE = 92/05/06 PTF IN ERROR = PIN = YES CURRENT APAR STATUS = CLOSED CLOSING CODE = DOC ORIGINAL APAR NUMBER = SECURITY/INTEGRITY = NO SERVICE NUMBER = 0462041 REPORTED COMPONENT = 568414101 R210 PSF/VM V2 R1.0 FIXED COMPONENT = FAILING MODULE = PROBLEM ABSTRACT: INCOMPLETE PROGRAM DIRECTORY FOR PSF/VM 2.1.0, PSF/VM 2.1.0 MANUAL INSTALL PROCEDURE REPORTED SCP RELEASE: 210 ERROR DESCRIPTION: Missing documentation after modification of aprftblv. System Programming Guide (s5443680-00 p233/4) refers to program directory but the whole documentation for manual installation procedure is missing there. This applies to build loadlibs and txtlibs for psf3800,psf3820. Applies to user which are using manual installation. UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN18912 PG 064 OF 076 TEMPORARY FIX: PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: PSF/VM 2.1.0 Installers * **************************************************************** * PROBLEM DESCRIPTION: The PSF/VM 2.1.0 Program Directory * * does not contain manual installation * * procedures. This information * * can only be found in the Washington * * Systems Center Flash 9120 entitled * * 'PSF/VM 2.1.0 Manual Install * * Procedure'. The customer requested * * that this FLASH also be made available * * in an APAR so that it could be found * * when searching for installation * * related help. * **************************************************************** * RECOMMENDATION: READ WSC FLASH 9120. * **************************************************************** UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN18912 PG 065 OF 076 PROBLEM CONCLUSION: A list of keywords was extracted from WSC FLASH 9120 and is included in this APAR so that any term found in this APAR will point to the FLASH document. RETAIN system limitations did not permit the inclusion of the entire FLASH in an APAR (as originally requested). . This APAR simply serves as an index into the FLASH. . AFPOPTS APRACTE APRACTEA APRACTEB APRACTEC APRACTES APRACTEV APRACTSL APRCALLL APRCALL4 APRFTBLV APRFTID APRFTIDB APRGP3AL APRGP3DL APRGP34A APRGP34D APRGRP4L APRGRP44 APRINIT APRINITV APRMAINL APRMTSK APROPRCL APROPRML APRPGRP4 APRPSFCC APRPSFCL APRPSFC4 APRP3820 APRRECEC APRSEPEC APRSETXL APRSFCMC APRSFCML APRSFCM4 APRSIOML APRSSCC APRSSCCL APRSSDAL APRSSDBL APRSSDDL APRSSPC APRWRKSL APRXCTLL ATTACH A00-A1F A00000 A20-A6F A20-A7F A20-A8F A20000 A60000 A80-ADF A80000 CHANNEL CLASSA CLASSc CLEAR CONTENTS COPY COPYFILE CP DCF3812 DCKVTBL DCKVTBLL DCKVTBL4 DCSS DEFSEG DMKSNT ESA EXAMPLE EXEC EXIT UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN18912 PG 066 OF 076 FILEDEF FLASH FORM FORMDEF FSF F1IBM GCS GENMOD GLOBAL GP3 Group3 Group4 GRP3 GRP3CHAN GRP3SNA GRP4 GRP4CHAN GRP4PDM GRP4SNA INSTALL INSTALLATION IVP I5684141 LIBE LINK LKED LKEDIT LOAD LOADLIB MAINT MANUAL MAP Meg megabyte member MEMO mode MODULE MOUNT nucleus OPERATOR OPR OPRMSG OPTIONS ORIGIN packing PAGEDEF PDM PDMGRP3 PDMGRP4 PDMREM1 PDM0490 PDM3800 PDM3820 PDM470 PEL PERM PPCC PRINT PROCEDURE PROFGRP3 PROFGRP4 PROFILE PROFS PROFSFCM PROF3800 PROF3820 PROTECT PSF PSF/VM PSFBASE PSFCMD PSFGRP3 PSFGRP3A PSFGRP3D PSFGRP4 PSFMAINT PSFPPCC PSF3800 PSF3820 RENT REP RESET resident resource resources REW RLDSAVE RPM SAVED SAVESEG SAVESYS SC230457 SEGMENT segments SETKEY SFCM shared SNA SPACE SR SYSLIN taskprtid TEXT TXTLIB TXTLIBSV verification VM/ESA VM/SP VM/XA VMFPLC2 WSC XA 19E 191 193 2.1.0 3800 3812 3820 5832 5852 5870 5892 7D0000 700-70F 700000 800-86F 800000 806-0004 9120 MODULES/MACROS: SRLS: G544368300 CIRCUMVENTION: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN18912 PG 067 OF 076 APPLICABLE COMPONENT LEVEL/SU: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN25215 PG 068 OF 076 APAR NUMBER = PN25215 LAST UPDATE = 92/07/31 PTF IN ERROR = PIN = YES CURRENT APAR STATUS = CLOSED CLOSING CODE = DOC ORIGINAL APAR NUMBER = SECURITY/INTEGRITY = NO SERVICE NUMBER = 0462041 REPORTED COMPONENT = 568414101 R210 PSF/VM V2 R1.0 FIXED COMPONENT = FAILING MODULE = PROBLEM ABSTRACT: APROPR336E ' ' IS NOT RECOGNIZED AS A COMMAND AFTER THE SFCM GOES INTO VM READ AND ENTER IS DEPRESSED AT THE MACHINE CONSOLE. REPORTED SCP RELEASE: 210 ERROR DESCRIPTION: MSAPROPR336E ' ' IS NOT RECOGNIZED AS A COMMAND when the ENTER key is depressed at the machine console. TEMPORARY FIX: PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: All PSF/VM 1.3.0 and 2.1.0 Customers who * UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN25215 PG 069 OF 076 * create their own SFCM installation exits. * **************************************************************** * PROBLEM DESCRIPTION: The SFCM hangs during processing of a * * print file. This occurs randomly. * * Upon further investigation, the SFCM is * * found to be in VM READ status and thus * * is effectively hung. In some * * installations, the SFCM id may even be * * forced off if it is inactive in VM READ * * status for too long. If ENTER is * * pressed (or any other keyboard input), * * the SFCM will issue message * * MSAPROPR336E 'command' IS NOT * * RECOGNIZED AS A COMMAND. The text in * * the message for 'command' will be * * whatever was entered at the console. * * If ENTER is pressed, it will be blanks. * **************************************************************** * RECOMMENDATION: Note the documentation change in this APAR. * UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN25215 PG 070 OF 076 **************************************************************** PROBLEM CONCLUSION: The problem described exposes a restriction that needs to be documented immediately and fixed eventually in the SFCM. The problem was a result of the installation modified SFCM separator page exit: APRSEPEC. The customer's APRSEPEC program makes use of the program stack. The SFCM program also makes use of the program stack. As a result, on some occasions the APRSEPEC program discarded incoming program stack items (placed on the stack by the SFCM interrupt handler APROPRC). The SFCM program keeps a count of these stacked items (which are incoming commands either from an operator or internal PSF SMSG commands from a PDM). APRSEPEC made use of the program stack and discarded these items. Later, the APRSEPEC program returns control back to the SFCM program, which attempts to process the 'stacked' commands. There are none. So, console input is required. When input is supplied, the SFCM processes the input as if it was an operator command and goes on. Although this UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN25215 PG 071 OF 076 scenario is disruptive, it is usually not harmful. However, this problem may cause the SFCM to become unsynchronized with the PDM programs it is converting for. For example, it may not learn that a PDM has been drained. The PSF/VM Change Team is responding to this problem in two ways: 1. The customer requirement to use the program stack in any SFCM installation exit without causing SFCM problems is accepted as a requirement for a future change in the product design ( SUG ). This requirement applies to SFCM installation exits APRSEPEC, APRACTEC, and APRRECEC as well as any SFCM installation exits which may be added to the product. 2. The PSF/VM System Programming Guide for 1.3.0 (566419801) publication number S5443467-03 page 194 and the PSF/VM System Programming Guide for 2.1.0 (568414101) publication UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN25215 PG 072 OF 076 number S5443680-00 page 221 are modified by adding the following paragraph at the end of the 'Providing and Modifying SFCM Exit Routines' section: 'Because the SFCM program uses the program stack, the SFCM installation exits should not use or modify the program stack.' MODULES/MACROS: SRLS: S544368000 S544346703 CIRCUMVENTION: APPLICABLE COMPONENT LEVEL/SU: UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN26757 PG 073 OF 076 APAR NUMBER = PN26757 LAST UPDATE = 92/09/01 PTF IN ERROR = PIN = YES CURRENT APAR STATUS = CLOSED CLOSING CODE = DOC ORIGINAL APAR NUMBER = SECURITY/INTEGRITY = NO SERVICE NUMBER = 0462041 REPORTED COMPONENT = 568414101 R210 PSF/VM V2 R1.0 FIXED COMPONENT = FAILING MODULE = PROBLEM ABSTRACT: MSDMSITP141T - OPERATION EXCEPTION, AND MSAPRABN559T X'0C1' AFTER APPLYING MAINTENANCE TO GROUP3 SAVED SEGMENT (ABENDS0C1). REPORTED SCP RELEASE: 210 ERROR DESCRIPTION: GRP3 DCSS overflowed after applying UN22830 (PN20587). Cust received MSDMSITP141T - operation exception occurred at x'000006' in routine APRINIT, and MSAPRABN559T - system abend abend0c1. The PSF/VM Program Directory is in error. On page 62, the example DMKSNT for SYSHRSG= should include 173, and the DEFSEG command should be A00-A5F instead of A00-A4F. The WSC UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN26757 PG 074 OF 076 Flash 9120 states the correct segment size. WSC FLASH 9120 is the PSF/VM Manual Installation Procedure. TEMPORARY FIX: PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: Users of the Group3 Channel PDM ( 2B9 ) who * * install PTF UN22830 for APAR PN20587 and * * have defined the APRGP34A shared segment * * DCSS as prescribed in the program * * directory. The PTF is on PUT9205. * **************************************************************** * PROBLEM DESCRIPTION: The referenced PTF causes the Group 3 * * PDM code to exceed five (5) 64K * * segments in length.This causes a branch * * to 0, resulting in the program check * * described. The type of program check * * depends on the data at address 0, and * * could have been specification * * exception, protection exception or * UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN26757 PG 075 OF 076 * addressing exception. 0C6 0C4 0C5 . * * ABEND0C4 ABEND0C5 ABEND0C6 * * The program directory should have * * always required 6 segments. * **************************************************************** * RECOMMENDATION: Redefine the APRGP34A segment if necessary * * before installing PTF UN22830 . * **************************************************************** Incorrect documentation caused progrAm check after installing PTF UN22830 PROBLEM CONCLUSION: In the Program Directory G5443683-00 page 62 change two lines: Figure 39 - SYSHRSG=(168-173), Do not omit the continuation character (X) In the next paragraph - DEFSEG APRGP34A A00-A5F SR MODULES/MACROS: SRLS: G544368300 UPGRADE: PSFVM210 SUBSET: VM/210 APAR PN26757 PG 076 OF 076 CIRCUMVENTION: APPLICABLE COMPONENT LEVEL/SU: