Re: JES2 Migration Function - Pros and Cons
Hi Liz, I'm running JES2 v2.2 @ RSU1703 and I've done the MERGE form of JES2 spool volume migration 7 times to mostly migrate our spool farm of 14 3390-27 volumes to 7 3390-54 volumes. I still have a few volumes to go to completely replace all of the 3390-27 volumes in this environment. Each time, I add a 3390-54 volume and migrate 2 3390-27 volumes to the 3390-54 volume. All of the migrations have been successful and we've had no problems occur as a result of the merge migration. Our migrations have taken about 15 minutes per volume, though that's probably a function of the utilization of the source volume. We age-delete our spool data after 5 days (held output) and 14 days (non-held) respectively, so this method is fundamentally similar to the old method of adding a new spool volume and halting source spool volumes, to replace spool volumes. After the $M command completes (maybe even during, I don't remember), the source volume is MAPPED to the target volume until all of the source volume data is age-deleted two weeks later and the source volume is DRAINed; I don't know if this philosophy is sanctioned by IBM but think of this as mapping the virtual spool volumes to physical dasd volumes, where the virtual volser can be different than the physical volser. The major difference between the old method and the $M MERGE method is that the physical dasd source volume is immediately available for reclaim by the dasd administrators after completion of the $M command, even though the data which previously resided on that volume still exists and JES2 tells you the data still resides on the source volume. Of course, the old source volser can't be added back to JES2 until the source volume is DRAINed. We're not able to use the MOVE form of JES2 spool migration in a real environment because our spool data is so large and actively changing that we can't afford to make the source volume INACTIVE prior to the migration, as is required for MOVE. The key to the MERGE migration is to use the output of $DSPL(),MIGDATA to ensure that the SPACE_USED quantity of the source volume is less than/equal to the LARGEST_FREE quantity of the target volume. You also need to ensure sufficient SPOOLDEF TGSPACE MAX capacity exists for both the source and target volumes (and any other volumes being used) to exist concurrently, until the source volume(s) are DRAINed. We generally $S the target volume and immediately do the merge migrations after target volume is formatted, to ensure a large output job doesn't jump in and claim some of that LARGEST_FREE space we were expecting to use for the MERGE migration. I hope that helps you. Please let me know if you have any specific questions. Dennis Schaffer -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
JESxEDS
I want to inform the JES2 community of a problem which has bitten us in testing JES2 v2.3. There's a new feature, called JES2 Email Delivery Services (EDS) in JES2 v2.3, which is intended to allow delivery of NOTIFY messages to an email address. The function is documented in a new manual: https://www-304.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3izsh100/$file/izsh100_v2r3.pdf. The key point, for this problem, is started task JESxEDS (where x is the identifier for the instance of JES2; 2, in our case) The symptom for our problem was inability to shutdown JES2 via $PJES2 (which is normal for us) or $PJES2,TERM (which is abnormal for us); a $PJES2,ABEND was required. IBM eventually determined that JES2 was waiting for stc JES2EDS (in our case) to shutdown. Furthermore, JES2 had either remembered that JES2EDS status across JES2 Quick starts or tried to restart JES2EDS during each JES2 initialization. But, since JES2EDS had never really started, it couldn't shutdown and JES2 waited indefinitely for an event which would never happen. The need for JES2 to start JES2EDS was triggered two days after we implemented JES2 2.3 in this environment, when a user submitted a job containing this statement "//LABEL NOTIFY USER=userid,TYPE=EMAIL", one of the triggers for this new EDS function. When JES2 executed this job, it attempted to create an email notification for this user and start JES2EDS. Unfortunately, we hadn't defined a RACF userid for JES2EDS yet and it failed to start. JES2, however, assumed that JES2EDS started normally and that set in motion the problems we experienced when we tried to shutdown JES2 a week later. In our case, IBM asked us to define RACF uid JES2EDS and to issue command "$S EDS" to request a start of JES2EDS. Based on dumps we took later, IBM told us that didn't really get JES2EDS started but it cleared the PCE wait flag which $PJES2,TERM had been waiting on; they think JES2EDS will start with the next JES2 initialization. IBM told us there really isn't a mechanism (a $D EDS command) to inquire the status of JES2EDS. We also weren't able to see address space JES2EDS (via D A,JES2EDS) after issuing "$S EDS" and IBM told us they saw the same (or lack thereof) on their system when they tried the same; however, that may have happened because JES2EDS really didn't start after "$S EDS". The key circumvention for this problem is to do whatever is necessary to allow JESxEDS to start; at a minimum, create a RACF userid for the task with at least minimal permissions to access SYS1.LINKLIB. I'd recommend all JES2 2.3 shops create this UID until the fix for this problem is available, even if you don't think you're using the EDS function. We didn't think so, either. IBM has written APAR OA55008 for this problem. Please let me know if you have any questions. Thanks, Dennis -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM z/OS PDF Documents - Page Can't Be Displayed
Thanks Susan, The publibz.boulder.ibm.com site seems to be working for IE11 today (actually, it was working last night but I wasn't in a position to respond at that time). Dennis -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM z/OS PDF Documents - Page Can't Be Displayed
Now, if there were a way to fix this for IE ... Some of us don't have access to Chrome or anything but IE, in this world of corporate deployments. Dennis -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM z/OS PDF Documents - Page Can't Be Displayed
Hi John, I was originally using IE11 when I experienced the problem. After seeing your response, I also tried Google Chrome and it worked! I'm not sure what would cause the difference but Thanks! Dennis -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IBM z/OS PDF Documents - Page Can't Be Displayed
Is anyone else having difficulty accessing IBM PDF manuals from http://www-03.ibm.com/systems/z/os/zos/library/bkserv/v2r2pdf/ ? Or http://www-03.ibm.com/systems/z/os/zos/library/bkserv/v2r1pdf/ ? I’m able to access these pages but when I try to select an individual PDF document to display, the browser clock spins for several seconds, then I get message “This page can’t be displayed”. I am able to display manuals from other vendors. I’ve also tried to save individual manuals w/ no success. This is happening on a Windows 7 PC on my corporate network but I get a similar error on an Ipad on an external network. I’m currently trying to download the entire PDF collection and that seems to be working, but slowly. Thanks, Dennis Schaffer -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
