|Planet MVS Dave's Program Products Pet Peeves Page|
|ANY RESEMBLANCE TO ANY LIVING OR DEAD PROGRAM PRODUCTS IS PURELY COINCIDENTAL.|
Why is it that every third party vendor in the world has no idea on how to package products under SMP/E ???. Perhaps (maybe) a little general, but each new product I have the misfortune to install reinforces the opinion. Some examples: i) "helpful" installer software. WRONG, WRONG, WRONG !!. If you ship software this way, at least make it so that it's aware of updates that were required to get it to work/install. ii) IEBCOPY of a heap of libraries, then Zonecopy of the SMP environment that just got uplifted. If you ship this way you are telling your customers you can't package properly, or don't trust your ability to do so. iii) "install these sysmods, then run these links OUTSIDE of SMP" - then maybe some more SMP work. You gotta be kidding ..... iv) "copy this install lib to disk then run the enclosed jobs". Except the JCL is wrong and/or the files referenced don't exist on the tape. v) PTFs shipped as USERMODs !!!. How many of you ACCEPT your USERMODs ?????. etc., etc. ...
U.K. translation: Welcome to the 1980's, ISPF supports colours in ISPF panels. For example, look at ISR@PRIM in OS/390 ISPF.
/* REXX - Invoke the XYZ Dialog */ address ISPEXEC "LIBDEF ISPLLIB DATASET ID('"SYS2.xyz.LOAD"')" "LIBDEF ISPPLIB DATASET ID('"SYS2.xyz.PANELS"')" "SELECT CMD(XYZ) NEWAPPL(XYZ) PASSLIB" "LIBDEF ISPLLIB DATASET" "LIBDEF ISPPLIB DATASET" exitUsing this LIBDEF method of invoking this product required no changes to the shop's ISPF concatenation or logon proc. A happy sysprog will be better disposed to recommend your future products.
SVCPARM 244,REPLACE,TYPE(3),EPNAME(XYZSVC) /* Vaporware, Inc. */
The default if SYSIN is dummy is to copy SYSUT1 to SYSUT2. The SYSUT3 and SYSUT4 work files haven't been used since the first Star Wars movies came out.//JUSTDOIT EXEC PGM=IEBCOPY //SYSUT3 DD DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL... //SYSUT4 DD DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL... //SYSPRINT DD SYSOUT=* //INDD DD ... //OUTDD DD ... //SYSIN DD * COPY INDD=INDD,OUTDD=OUTDD /*
//JUSTDOIT EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //SYSUT1 DD ... //SYSUT2 DD ... //SYSIN DD DUMMY
Okay, the only time this is a problem is when there is so much JCL on one line and you don't have room enough for a "C 'SL)' 'SL,,,EXPDT=98000)' all". This has happened to me two or three times this year.//SYSUT1 DD DISP=(OLD,KEEP), // LABEL=(x,SL), Non-TMS //* LABEL=(x,SL,,,EXPDT=98000), TMS //* LABEL=(x,BLP), Bypass Label Processing // ...other parms here...
VENDORS: Please support "P taskname". Our time is valuable. Our operators have better things to do than look up the syntax of your lame product's commands. If operations calls us at three in the morning all the time, we are going to start hating your company and will NOT buy anymore of your lame products.R 22,SHUT IMM IEE600I REPLY TO 22 IS;SHUT IMMDrats, the NETVIEW shutdown command doesn't stop IDMSR 23,CEMT P SHUTDOWN IEE600I REPLY TO 23 IS;CEMT P SHUTDDrats, the CICS shutdown command doesn't shutdown IDMSR 24,CEMT SHUT IEE600I REPLY TO 24 IS;CEMT SHUTDrats, another variation on the CICS shutdown command didn't stop IDMS. I guess I'll crack open the procedures manual.
"CPF also ensures that two or more systems do not have the same or overlapping prefixes, which helps prevent confusion."The CPF macro looks pretty easy to code.
|THE VIEWS ON THIS PAGE DO NOT REPRESENT THE VIEWS OF MY PAST, CURRENT AND FUTURE EMPLOYERS.|