Power PDelete - CRDATE
David Stuart
A question about the CRDATE option of the Power PDelete command. I was hoping there was the ability to specify a date in number of days in some way, although I can't find anything in Power Admin/Ops.
Ideally, I would like to be able to delete anything with a specified job name that is over, say, 5 days old, and I was thinking the CRDATE might have that capability.
Yes, I know I can code a Rexx proc to calculate the date, etc., but was hoping that there was something available already.
And just because there is nothing in the books doesn't mean the capability doesn't exist (hope, hope!).
TIA,
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
David....@ventura.org
Wakser, David
positive response!
David Wakser
Bill Barthel
Anybody out there running VSE 2.3 on a z9 box? We are replacing our 7060 with a 2096-C01 and will be upgrading our VSE to 4.1 but have the need to run our current VSE during conversion. Our business partner identified a couple of PTFs they thought we might need (DY45944 and DY45958).
Any information would be appreciated.
Bill Barthel
Systems & Operations Supervisor
County of Merced
Email: bbar...@co.merced.ca.us
Phone: (209) 385-7507
K Meyer
If you have BIM-FAQS/ASO, you could use 'D LST,CRDAYS>nn' and then
use the L from the screen. :-)
Otherwise, you could create a list of entries and then delete them
using some form of automation.
Ken Meyer
CSI
*********** REPLY SEPARATOR ***********
On 7/2/2008 at 9:45 AM Wakser, David wrote:
snip..
Frank M. Ramaekers
Frank M. Ramaekers Jr.
Systems Programmer MCP, MCP+I, MCSE & RHCE
American Income Life Insurance Co. Phone: (254)761-6649
1200 Wooded Acres Dr. Fax: (254)741-5777
Waco, Texas 76710
-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf
Of David Stuart
Sent: Wednesday, July 02, 2008 11:42 AM
To: VSE Discussion List
Subject: Power PDelete - CRDATE
Morning all,
TIA,
Dave
_____________________________________________________
This message contains information which is privileged and confidential and is solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any review, disclosure,
copying, distribution, or use of the contents of this message is strictly prohibited. If you have
received this in error, please destroy it immediately and notify us at Priva...@ailife.com.
indust...@winwholesale.com
> Anybody out there running VSE 2.3 on a z9 box?
I can only attest to running VSE 2.3 (with the patches you mention)
on a z890 box while we installed and tested z/VSE 2.6, 2.7, and 3.1.2 in a
second LPAR before finally moving z/VSE 3.1.2 into production and getting
rid of VSE 2.3 only 10 or 12 years late. ;-)
Sincerely,
Dave Clark
WinWholesale Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
indust...@winwholesale.com
> Yes, I know I can code a Rexx proc to calculate the date, etc.,
> but was hoping that there was something available already.
Too easy to do it in VSE/REXX:
usrdate = Date('USA', Date('Base') - 5, 'Base');
Address POWER 'PDELETE LST,ALL,CRDATE<'usrdate;
Kevin Corkery
D LST,MYJOB*,RDAYS>10
Would display all reports for jobs beginning in MYJOB created more than 10 days ago.
Of course, you could use the same selection criteria in the PDELETE command.
--
Kevin Corkery
Independent Consultant
Voorhees, New Jersey
-------------- Original message ----------------------
From: "Frank M. Ramaekers" <FRama...@ailife.com>
> I had asked for that awhile ago, but couldn't stir up enough interest.
>
> Frank M. Ramaekers Jr.
> Systems Programmer MCP, MCP+I, MCSE & RHCE
> American Income Life Insurance Co. Phone: (254)761-6649
> 1200 Wooded Acres Dr. Fax: (254)741-5777
> Waco, Texas 76710
>
>
> -----Original Message-----
> From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf
> Of David Stuart
> Sent: Wednesday, July 02, 2008 11:42 AM
> To: VSE Discussion List
> Subject: Power PDelete - CRDATE
>
> Morning all,
>
> A question about the CRDATE option of the Power PDelete command. I was
> hoping there was the ability to specify a date in number of days in some
> way, although I can't find anything in Power Admin/Ops.
>
> Ideally, I would like to be able to delete anything with a specified job
> name that is over, say, 5 days old, and I was thinking the CRDATE might
> have that capability.
>
> Yes, I know I can code a Rexx proc to calculate the date, etc., but was
> hoping that there was something available already.
>
Kevin Corkery
Jeffrey Barnard
You do not say anything about z/VM. A google search of this list for '2.3
and z9' did not show anyone running VSE/ESA 2.3 on a z9 without z/VM
5.2/5.3 even with the APARs you refer to.
There was a post about problem a with CICS TS transactions hanging in
USERWAIT that went away when they went from VSE 2.6 to z/VSE. But since you
are VSE 2.3 and running CICS/CSE 2.3 this is not an issue.
Try a google search on this list for the APARs you referred to ... Might
get some results there too.
Regards,
Jeff
--
Jeffrey C Barnard
Barnard Software, Inc. http://www.bsiopti.com
BSI 407-323-4773 Support 407-688-7123
Fazzito, Marcelo
Bill,
We were running zVM 3.1 and VSE/ESA 2.3 in a z890.
Needing to upgrade, the z9 was the option so we migrated first to zVM 5.3 and started to migrate to zVSE 3.1.
We are running now in the Backup z890, did the upgrade to the production z890 and it is now a z9 S07. we are running on it the test zVM and the test VSE 2.3 due to we only migrated to zVSE 3 of 8 VSE's.
Production VSE's will start running in the z9 on next Sunday 13. Up to this moment everything is running fine, just for testing.
We applied no PTF's added to the ones applied when upgraded to z890 ( the ones you mention)
Regards. Marcelo.
How to apply the supervisor patches to your VSE/ESA 2.3 system
The following patches for phase $$A$IPLR and the supervisor phases $$A$SUPX and
$$A$SUPI apply to the latest VSE/ESA 2.3 maintenance level:
// JOB CORRECT PHASE
// EXEC MSHP
CORRECT 5686-06-606-35C : DY45944
AFFECTS PHASES=$$A$IPLR
ALTER 34A6 D2019066C546:D70190669066 /* SVIMCELL STCHNXT9 */
AFFECTS PHASES=$$A$SUPX
ALTER 5A274 58500710:45A00380 /* BAL PATCH FREEPMT+ */
ALTER 380 40404040:58500710 /* REINSTALL INSTR */
ALTER 384 40404040:900F0F0C /* DISPMAC */
ALTER 388 40404040:41F000C0 /* FUNC=PTLB */
ALTER 38C 40404040:58D008A4 /* */
ALTER 390 4040:0CED /* */
ALTER 392 40404040:980F0F0C /* */
ALTER 396 4040:07FA /* RETURN */
AFFECTS PHASES=$$A$SUPI
ALTER 5C5F4 58500710:45A00380 /* BAL PATCH FREEPMT+ */
ALTER 380 40404040:58500710 /* REINSTALL INSTR */
ALTER 384 40404040:900F0F0C /* DISPMAC */
ALTER 388 40404040:41F000C0 /* FUNC=PTLB */
ALTER 38C 40404040:58D008A4 /* */
ALTER 390 4040:0CED /* */
ALTER 392 40404040:980F0F0C /* */
ALTER 396 4040:07FA /* RETURN */
RESOLVES 'DY45944 DY45958'
/*
/&
Please perform the following steps for the supervisor phases (AFFECTS
PHASES=$$A$SUPX, $$A$SUPI or other supervisor phase), if you are not on the latest
VSE/ESA 2.3 maintenance level:
1. Scan for character string "FREEPMT" (e.g. via the AR LOCATE command)
2. Subtract X'24' from the address you located.
3. The resulting address should point to instruction "58500710".
4. Use that address and replace it in the first ALTER statement for each supervisor
patch; e.g. patch for $$A$SUPX = replace address 5A274
5. Implement the patch for all supervisors you want to IPL on the new z890, z990 or
System z9.
"Este mensaje y sus anexos son confidenciales y para uso exclusivo del titular de la dirección de correo electrónico a que está dirigido. Puede contener información amparada por el secreto bancario cuyo uso inadecuado puede derivar en responsabilidad civil y/o penal. Por lo expuesto, su contenido no debe ser copiado, enviado, revelado o utilizado por personas distintas de su destinatario. Si Ud. no fuera el destinatario especificado en el mensaje o persona autorizada por éste, informe de tal situación reenviando el mensaje al emisor e inmediatamente proceda a borrar el mensaje recibido y sus adjuntos. No se garantiza la seguridad o la exactitud de lo transmitido, ya que el correo electrónico remitido pudo haber sido interceptado, modificado o contener virus informáticos u otras anomalías. El Bco. Credicoop C.L. no tiene intención de generar correo no deseado, pero si Ud. entiende que está siendo afectado por esta práctica, reenvíelo a: cal...@bancocredicoop.coop."