Re: SDSF and z/OSEM and Automation
I use SDSF / REXX for running jobs. You would just change the code for jobs on input queue status. Code snippet... /* ACCESS THE ST DISPLAY */ PARSE VALUE IPARM WITH JOBPREF ',' TIMEOUT ISFCMDX = "ISFEXEC ST " ||JOBPREF||"*" ADDRESS SDSF ISFCMDX LRC=RC CALL MSGRTN IF LRC<>0 THEN EXIT 20 /* LOOP FOR ALL RUNNING JOBS SPECIFIED IN PARAMETER */ say jname.0 JOBPREF||'*' ' JOBS FOUND' /* */ DO IX=1 TO JNAME.0 IF POS(JOBPREF,JNAME.IX) > 0 & , QUEUE.IX = "EXECUTION" & , ACTSYS.IX <> "" THEN DO This particular code is used to find long running jobs and cancel them if they have been running more than 2 hours. We have a training region where users submit batch queries that can potentially run for hours and affect batch schedules. Liam Doherty from IBM gave a presentation on this at a SHARE conference a few years ago. On Sat, Oct 20, 2018 at 3:37 AM Lizette Koehler wrote: > So I want to create a process that "notices" that a job has been in the > JES2 > Input queue for over 24 hours and not run. > > Sometimes this is legitimate and sometimes not. > > With z/OSEM we add resource names so the users do not need to code /*ROUTE > XEQ > lpar to run. > > What I find is sometimes the resource name created in the JCL is not valid > for > the environment. > > I know I can issue $DJ,LONG and find out what resource it is waiting > on. > > What I am struggling with is how can I see the INPUT queue and determine > how > long a job has been waiting. > > I am thinking something with ISFEXEC (SDSF) that I can pass to automation > to > make the determination and/or cancel of the task. > > I am just in the design phase, so no real details other than this sketch > of the > process. > > Thanks > > > Lizette > A theory can never be proven, but it can be falsified. Karl Raimund Popper > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I list the contents of a ADRDSSU DUMP dataset?
As Alan says, TYPRUN=NORUN. I always use it before I run a DUMP, just to get a list of what will be covered. On Sat, Oct 20, 2018 at 6:52 AM Allan Staller wrote: > //S1 EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN' > > //SYSINDD * > RESTORE DSN(**) . > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Jerry Callen > Sent: Friday, October 19, 2018 2:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: How can I list the contents of a ADRDSSU DUMP dataset? > > I'd like to be able to list the names of the files present in a "logical > dump" dataset produced by ADRDSSU. AFAIK, there isn't a command to ADRDSSU > to do that (seems like an odd omission...). > > The format of the dump dataset is thoroughly described: > > > https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.adru000%2Ffmtdds.htm&data=02%7C01%7Callan.staller%40HCL.COM%7C509ce9f007b946febb3108d635fbd60e%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636755753110341477&sdata=kaTSFGDA4BL3eC9Zce6CEtP%2FOL4JXryYkcJwtK5rBtw%3D&reserved=0 > > But I really don't want to have to write the code to grovel over the > dataset and format this stuff if someone else has already done it. :-) > > I looked on the CBT Tape; no joy. > > Any suggestions? > > -- Jerry > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ::DISCLAIMER:: > > -- > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain > viruses in transmission. The e mail and its contents (with or without > referred errors) shall therefore not attach any liability on the originator > or HCL or its affiliates. Views or opinions, if any, presented in this > email are solely those of the author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, distribution and / or > publication of this message without the prior written consent of authorized > representative of HCL is strictly prohibited. If you have received this > email in error please delete it and notify the sender immediately. Before > opening any email and/or attachments, please check them for viruses and > other defects. > > -- > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I list the contents of a ADRDSSU DUMP dataset?
//S1 EXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN' //SYSINDD * RESTORE DSN(**) . -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jerry Callen Sent: Friday, October 19, 2018 2:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: How can I list the contents of a ADRDSSU DUMP dataset? I'd like to be able to list the names of the files present in a "logical dump" dataset produced by ADRDSSU. AFAIK, there isn't a command to ADRDSSU to do that (seems like an odd omission...). The format of the dump dataset is thoroughly described: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.adru000%2Ffmtdds.htm&data=02%7C01%7Callan.staller%40HCL.COM%7C509ce9f007b946febb3108d635fbd60e%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636755753110341477&sdata=kaTSFGDA4BL3eC9Zce6CEtP%2FOL4JXryYkcJwtK5rBtw%3D&reserved=0 But I really don't want to have to write the code to grovel over the dataset and format this stuff if someone else has already done it. :-) I looked on the CBT Tape; no joy. Any suggestions? -- Jerry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How can I list the contents of a ADRDSSU DUMP dataset?
Convert to FDR/ABR :) -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jerry Callen Sent: Friday, October 19, 2018 3:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: How can I list the contents of a ADRDSSU DUMP dataset? [External Email] I'd like to be able to list the names of the files present in a "logical dump" dataset produced by ADRDSSU. AFAIK, there isn't a command to ADRDSSU to do that (seems like an odd omission...). The format of the dump dataset is thoroughly described: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.adru000/fmtdds.htm But I really don't want to have to write the code to grovel over the dataset and format this stuff if someone else has already done it. :-) I looked on the CBT Tape; no joy. Any suggestions? -- Jerry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN FIRST TENNESSEE Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
How can I list the contents of a ADRDSSU DUMP dataset?
I'd like to be able to list the names of the files present in a "logical dump" dataset produced by ADRDSSU. AFAIK, there isn't a command to ADRDSSU to do that (seems like an odd omission...). The format of the dump dataset is thoroughly described: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.adru000/fmtdds.htm But I really don't want to have to write the code to grovel over the dataset and format this stuff if someone else has already done it. :-) I looked on the CBT Tape; no joy. Any suggestions? -- Jerry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF and z/OSEM and Automation
As with anything we do there are different ways to get the info. Using the command $D JQ,DELAY=YES will get you a list and then you can go from there. Bottom line you do what works best for your environment. $D JQ,DELAY=YES $HASP890 JOB(UI0351DA) $HASP890 JOB(UI0351DA) STATUS=(AWAITING EXECUTION),CLASS=Q, $HASP890PRIORITY=0,SYSAFF=(PR01,PR04,PR03), $HASP890HOLD=(JOB),DELAY=(HOLD) $HASP890 JOB(UI0351PC) $HASP890 JOB(UI0351PC) STATUS=(AWAITING EXECUTION),CLASS=Q, $HASP890PRIORITY=0,SYSAFF=(PR01,PR04,PR03), $HASP890HOLD=(JOB),DELAY=(HOLD) $HASP890 JOB(UDT014OP) $HASP890 JOB(UDT014OP) STATUS=(AWAITING EXECUTION),CLASS=Q, $HASP890PRIORITY=9,SYSAFF=(PR03),HOLD=(JOB), $HASP890DELAY=(HOLD,MEMBER_STATUS) Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Barkow, Eileen Sent: Friday, October 19, 2018 12:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SDSF and z/OSEM and Automation You would have to know each job name/number in advance for the $DJ,LONG. SDSF can show the entire input queue - you just select each task, get the start time, and cancel it if needed directly from SDSF. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Shorkend Sent: Friday, October 19, 2018 1:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SDSF and z/OSEM and Automation The $DJ,LONG command returns a field with the job creation date and time. You could pull this with REXX and the CONSOLE command and then do the math. $DJ(827),LONG $HASP890 JOB(MIKEBR14) 536 $HASP890 JOB(MIKEBR14) STATUS=(AWAITING EXECUTION),CLASS=Z, $HASP890PRIORITY=7,SYSAFF=(ANY),HOLD=(NONE), $HASP890CMDAUTH=(LOCAL),OFFS=(),SECLABEL=, $HASP890USERID=MIKE,SPOOL=(VOLUMES=(VPSPOL), $HASP890TGS=1,PERCENT=0.0052),ARM_ELEMENT=NO, $HASP890CARDS=2,DUBIOUS=NO,REBUILD=NO, $HASP890SRVCLASS=BATMDM,SCHENV=,SCHENV_AFF=(ANY), $HASP890CC=(),DELAY=(),CRTIME=(2018.292,17:13:56) Note that the time returned is UTC and not local HTH Mike On Fri, 19 Oct 2018 at 19:36, Lizette Koehler wrote: > So I want to create a process that "notices" that a job has been in > the > JES2 > Input queue for over 24 hours and not run. > > Sometimes this is legitimate and sometimes not. > > With z/OSEM we add resource names so the users do not need to code > /*ROUTE XEQ lpar to run. > > What I find is sometimes the resource name created in the JCL is not > valid for the environment. > > I know I can issue $DJ,LONG and find out what resource it is > waiting on. > > What I am struggling with is how can I see the INPUT queue and > determine how long a job has been waiting. > > I am thinking something with ISFEXEC (SDSF) that I can pass to > automation to make the determination and/or cancel of the task. > > I am just in the design phase, so no real details other than this > sketch of the process. > > Thanks > > > Lizette > A theory can never be proven, but it can be falsified. Karl Raimund > Popper > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Mike Shorkend m...@shorkend.com www.shorkend.com Tel: +972524208743 Fax: +97239772196 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF and z/OSEM and Automation
You would have to know each job name/number in advance for the $DJ,LONG. SDSF can show the entire input queue - you just select each task, get the start time, and cancel it if needed directly from SDSF. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Shorkend Sent: Friday, October 19, 2018 1:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SDSF and z/OSEM and Automation The $DJ,LONG command returns a field with the job creation date and time. You could pull this with REXX and the CONSOLE command and then do the math. $DJ(827),LONG $HASP890 JOB(MIKEBR14) 536 $HASP890 JOB(MIKEBR14) STATUS=(AWAITING EXECUTION),CLASS=Z, $HASP890PRIORITY=7,SYSAFF=(ANY),HOLD=(NONE), $HASP890CMDAUTH=(LOCAL),OFFS=(),SECLABEL=, $HASP890USERID=MIKE,SPOOL=(VOLUMES=(VPSPOL), $HASP890TGS=1,PERCENT=0.0052),ARM_ELEMENT=NO, $HASP890CARDS=2,DUBIOUS=NO,REBUILD=NO, $HASP890SRVCLASS=BATMDM,SCHENV=,SCHENV_AFF=(ANY), $HASP890CC=(),DELAY=(),CRTIME=(2018.292,17:13:56) Note that the time returned is UTC and not local HTH Mike On Fri, 19 Oct 2018 at 19:36, Lizette Koehler wrote: > So I want to create a process that "notices" that a job has been in > the > JES2 > Input queue for over 24 hours and not run. > > Sometimes this is legitimate and sometimes not. > > With z/OSEM we add resource names so the users do not need to code > /*ROUTE XEQ lpar to run. > > What I find is sometimes the resource name created in the JCL is not > valid for the environment. > > I know I can issue $DJ,LONG and find out what resource it is > waiting on. > > What I am struggling with is how can I see the INPUT queue and > determine how long a job has been waiting. > > I am thinking something with ISFEXEC (SDSF) that I can pass to > automation to make the determination and/or cancel of the task. > > I am just in the design phase, so no real details other than this > sketch of the process. > > Thanks > > > Lizette > A theory can never be proven, but it can be falsified. Karl Raimund > Popper > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Mike Shorkend m...@shorkend.com www.shorkend.com Tel: +972524208743 Fax: +97239772196 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF and z/OSEM and Automation
And that is why I asked. I was making it too complicated. Thank you very much > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Barkow, Eileen > Sent: Friday, October 19, 2018 10:16 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SDSF and z/OSEM and Automation > > You really do not need automation for this except to kick off a task that > uses SDSF/REXX to issue an "I" command to see the input queues and Then > select each entry to see the date/time the job was submitted. > You can find sample SDSF/REXX clists in the manual which do similar things or > I have some written which I can share with you. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Friday, October 19, 2018 12:37 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SDSF and z/OSEM and Automation > > So I want to create a process that "notices" that a job has been in the JES2 > Input queue for over 24 hours and not run. > > Sometimes this is legitimate and sometimes not. > > With z/OSEM we add resource names so the users do not need to code /*ROUTE > XEQ lpar to run. > > What I find is sometimes the resource name created in the JCL is not valid > for the environment. > > I know I can issue $DJ,LONG and find out what resource it is waiting on. > > What I am struggling with is how can I see the INPUT queue and determine how > long a job has been waiting. > > I am thinking something with ISFEXEC (SDSF) that I can pass to automation to > make the determination and/or cancel of the task. > > I am just in the design phase, so no real details other than this sketch of > the process. > > Thanks > > > Lizette > A theory can never be proven, but it can be falsified. Karl Raimund Popper > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > This e-mail, including any attachments, may be confidential, privileged or > otherwise legally protected. It is intended only for the addressee. If you > received this e-mail in error or from someone who was not authorized to send > it to you, do not disseminate, copy or otherwise use this e-mail or its > attachments. Please notify the sender immediately by reply e-mail and delete > the e-mail from your system. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF and z/OSEM and Automation
The $DJ,LONG command returns a field with the job creation date and time. You could pull this with REXX and the CONSOLE command and then do the math. $DJ(827),LONG $HASP890 JOB(MIKEBR14) 536 $HASP890 JOB(MIKEBR14) STATUS=(AWAITING EXECUTION),CLASS=Z, $HASP890PRIORITY=7,SYSAFF=(ANY),HOLD=(NONE), $HASP890CMDAUTH=(LOCAL),OFFS=(),SECLABEL=, $HASP890USERID=MIKE,SPOOL=(VOLUMES=(VPSPOL), $HASP890TGS=1,PERCENT=0.0052),ARM_ELEMENT=NO, $HASP890CARDS=2,DUBIOUS=NO,REBUILD=NO, $HASP890SRVCLASS=BATMDM,SCHENV=,SCHENV_AFF=(ANY), $HASP890CC=(),DELAY=(),CRTIME=(2018.292,17:13:56) Note that the time returned is UTC and not local HTH Mike On Fri, 19 Oct 2018 at 19:36, Lizette Koehler wrote: > So I want to create a process that "notices" that a job has been in the > JES2 > Input queue for over 24 hours and not run. > > Sometimes this is legitimate and sometimes not. > > With z/OSEM we add resource names so the users do not need to code /*ROUTE > XEQ > lpar to run. > > What I find is sometimes the resource name created in the JCL is not valid > for > the environment. > > I know I can issue $DJ,LONG and find out what resource it is waiting > on. > > What I am struggling with is how can I see the INPUT queue and determine > how > long a job has been waiting. > > I am thinking something with ISFEXEC (SDSF) that I can pass to automation > to > make the determination and/or cancel of the task. > > I am just in the design phase, so no real details other than this sketch > of the > process. > > Thanks > > > Lizette > A theory can never be proven, but it can be falsified. Karl Raimund Popper > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Mike Shorkend m...@shorkend.com www.shorkend.com Tel: +972524208743 Fax: +97239772196 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF and z/OSEM and Automation
You really do not need automation for this except to kick off a task that uses SDSF/REXX to issue an "I" command to see the input queues and Then select each entry to see the date/time the job was submitted. You can find sample SDSF/REXX clists in the manual which do similar things or I have some written which I can share with you. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Friday, October 19, 2018 12:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SDSF and z/OSEM and Automation So I want to create a process that "notices" that a job has been in the JES2 Input queue for over 24 hours and not run. Sometimes this is legitimate and sometimes not. With z/OSEM we add resource names so the users do not need to code /*ROUTE XEQ lpar to run. What I find is sometimes the resource name created in the JCL is not valid for the environment. I know I can issue $DJ,LONG and find out what resource it is waiting on. What I am struggling with is how can I see the INPUT queue and determine how long a job has been waiting. I am thinking something with ISFEXEC (SDSF) that I can pass to automation to make the determination and/or cancel of the task. I am just in the design phase, so no real details other than this sketch of the process. Thanks Lizette A theory can never be proven, but it can be falsified. Karl Raimund Popper -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SCP of file to USS from Mac is corrupted
On Thu, 18 Oct 2018 18:06:34 -0700, Tom Brennan wrote: > > beautiful EBCDIC encoding and the podunk, 7-bit, toy-computer ASCII >encoding > >Poking the I HATE EBCDIC bear? :) > If the reader ignores the bigotry, he stated a true fact about ASCII. But it's irrelevant since ssh (and I assume scp) don't use ASCII. >When I wrote up some doc showing application programmers how to setup >mainframe SSH keys, the example showed scp to transfer the text public >key to the non-mainframe box. It was less error-prone since the >translation to ASCII was built in and (I think) impossible to turn off. > And thus an impediment to transferring a pax file. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF and z/OSEM and Automation
Lizette, you can also see the create date time (CRTIME) of the job. Is that good enough for what you want? As I look at this the interesting thing I see on my system the time is UCT and not US central time. I'll have to look at that. :) $DJ(95379),LONG $HASP890 JOB(UDT014OP) $HASP890 JOB(UDT014OP) STATUS=(AWAITING EXECUTION),CLASS=Q, $HASP890PRIORITY=9,SYSAFF=(PR03),HOLD=(JOB), $HASP890CMDAUTH=(LOCAL),OFFS=(),SECLABEL=, $HASP890USERID=UDT014,SPOOL=(VOLUMES=(OSSPP4), $HASP890TGS=1,PERCENT=0.),ARM_ELEMENT=NO, $HASP890CARDS=15,DUBIOUS=NO,REBUILD=NO, $HASP890SRVCLASS=TSPBATHI, $HASP890SCHENV=TESTJOB(SET BY OPERATOR), $HASP890SCHENV_AFF=(PR01),CC=(),DELAY=(HOLD, $HASP890MEMBER_STATUS), $HASP890CRTIME=(2018.292,17:01:24),JOBGROUP= Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Friday, October 19, 2018 11:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SDSF and z/OSEM and Automation So I want to create a process that "notices" that a job has been in the JES2 Input queue for over 24 hours and not run. Sometimes this is legitimate and sometimes not. With z/OSEM we add resource names so the users do not need to code /*ROUTE XEQ lpar to run. What I find is sometimes the resource name created in the JCL is not valid for the environment. I know I can issue $DJ,LONG and find out what resource it is waiting on. What I am struggling with is how can I see the INPUT queue and determine how long a job has been waiting. I am thinking something with ISFEXEC (SDSF) that I can pass to automation to make the determination and/or cancel of the task. I am just in the design phase, so no real details other than this sketch of the process. Thanks Lizette A theory can never be proven, but it can be falsified. Karl Raimund Popper -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Hyperswap option in HMC
Hi Good morning all I see hyperswap option is meant for storage. How does HMC connects the storage via hyperswap ? Just curious to know for my knowledge purpose and I apologise for being ignorant Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SDSF and z/OSEM and Automation
So I want to create a process that "notices" that a job has been in the JES2 Input queue for over 24 hours and not run. Sometimes this is legitimate and sometimes not. With z/OSEM we add resource names so the users do not need to code /*ROUTE XEQ lpar to run. What I find is sometimes the resource name created in the JCL is not valid for the environment. I know I can issue $DJ,LONG and find out what resource it is waiting on. What I am struggling with is how can I see the INPUT queue and determine how long a job has been waiting. I am thinking something with ISFEXEC (SDSF) that I can pass to automation to make the determination and/or cancel of the task. I am just in the design phase, so no real details other than this sketch of the process. Thanks Lizette A theory can never be proven, but it can be falsified. Karl Raimund Popper -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CHPIDs for HyperSwap Target Subsystem
When setting up a HyperSwap target subsystem in HCD does anyone know if the same CHPIDs have to be used or can you use different CHPIDs? We have a subsystem with 20480 Mod-54 devices that we need to be able to HyperSwap to a new subsystem. I'm unable to use the same CHPIDs for both due to exceeding the number of devices per CHPID, 32760, by 8192. I can define new CHPIDs for the HyperSwap target subsystem but they would only be used while we were in a HyperSwap situation, not very often we're hoping. Ken Mazer -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: get ECSA key 7 storage under CICS
Presumably you're trying to avoid buying a commercial product to do this. It appears to me this should be a "buy" rather than a "make". Thanks, Martin Martin Packer zChampion, Systems Investigator & Performance Troubleshooter, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker Podcast Series (With Marna Walle): https://developer.ibm.com/tv/mpt/or https://itunes.apple.com/gb/podcast/mainframe-performance-topics/id1127943573?mt=2 Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA From: Wang Rong To: IBM-MAIN@LISTSERV.UA.EDU Date: 19/10/2018 10:50 Subject:Re: get ECSA key 7 storage under CICS Sent by:IBM Mainframe Discussion List Hi Binyamin, Thanks for your suggestion, I will consider doing that via batch/started task. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: get ECSA key 7 storage under CICS
Hi Binyamin, Thanks for your suggestion, I will consider doing that via batch/started task. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
