Re: z/OS holddata per https?

I don't any more, because we're winding down. But, is there a good reason not to run a RECEIVE order frequently, like even daily? > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Barbara Nitz > Sent: Monday, January 11, 2021 10:12 PM > To:

Re: z/OS holddata per https?

Classification: Limited You can use RECEIVE ORDER to just get HOLDDATA. RECEIVE ORDER( ORDERSERVER(ORDRINFO) CONTENT(HOLDDATA) CLIENT(CLNTINFO) ) Andy Styles z/Series System

Re: Ibm macro instructions code clarification

Are there any other messages issued at the same time? Also, by "our product" do you mean it is written by your organisation? Roops On Tue., Jan. 12, 2021, 06:54 Jake Anderson, wrote: > Hello > > Apologies for my ignorance. One of our product failed with FDBWD : 00141300 > FDBK2. > > I am not

Re: Request for help with removing sequence numbers from PDS members

On 2021-01-11 8:06 PM, Sean Gleann wrote: Can anyone point me at some sort of solution that I might adapt, please? Perhaps there is something on the CBT tape that might help... I am sure the original problem has been resolved by now, but for completeness I will mention a couple of things

Re: z/OS holddata per https?

> RECEIVE >ORDER( >ORDERSERVER(ORDRINFO) >CONTENT(HOLDDATA) > CLIENT(CLNTINFO) > ) Thanks for that, Andy. I looked at the SMPE cmd reference and didn't see the solution. We are a small

Re: Request for help with removing sequence numbers from PDS members

I've been told by Powers That Be that this line of development is redundant & that a different solution has been independently developed elsewhere in the company. (*sigh* - 'twas ever thus) But I'm still interested in discovering what I'm doing wrong. To that end, here's the jobstream I'm using,

Interchip's RTD/DB2

Anyone use Interchip's Real Time Defrag for DB2?   Does it work well?  Any gotchas?  Other comments? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message:

Re: Request for help with removing sequence numbers from PDS members

On Tue, 12 Jan 2021 11:26:32 +, Sean Gleann wrote: > > 7 *-* "ISREDIT MACRO" > >L> "ISREDIT MACRO" > +++ RC(20) +++ > That belongs not here but in your initial macro. >21 *-* "ISPEXEC EDIT DATAID() MEMBER() MACRO()" > >L> "ISPEXEC EDIT DATAID() MEMBER()

Re: Interchip's RTD/DB2

We didn't have that specific product, just their standard dataset RTD. It consumed lots of CPU cycles. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On

Re: Ibm macro instructions code clarification

I think that's the problem: he does not know. They run some program for which the source code is not readily available. It fails, with the message FDBWD : 00141300 FDBK2. He knows that is insufficient information but wants to know if anyone here recognizes it, goes "oh yeah, that would be a

Re: Interchip's RTD/DB2

It works really well when customised and set up properly for your environment. I would recommend it. Interchip's support is excellent and they resolve any issues really quick. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Tuesday, January 12,

Re: z/OS holddata per https?

Other solution: just circumvent restrictions. Simply download HOLDDATA using private PC and then send it via email. Yes, it is a crime... but it works. Of course it would require some effort to understand that it is possible to allow ftp to IBM site, especially limited to few persons which have

Re: Request for help with removing sequence numbers from PDS members

Twice recently I've tried to paste an answer to a question involving some REXX output and been caught by our DLP filters. Subscribing separately to avoid that! Anyway, is it just that you're seeing the RC20 from the ISREDIT? I would expect that on the first invocation, the CONTROL ERRORS

Re: Ibm macro instructions code clarification

Really vague. What function are you trying to do? I am used to those fields being VSAM, and they are documented in the DFSMS manuals. But were you doing an OPEN, or a GET, or a PUT, or a CLOSE, or something else? What is the Return Code (Register 15)? Are you using RLS or TVS? What version of

Re: Request for help with removing sequence numbers from PDS members

Hi Andy "is it just that you're seeing the RC20 from the ISREDIT" - in this particular version of the REXX it is, but as previously detailed I had problems with the syntax of the CONTROL ERRORS statement. "Does the REXX continue afterwards if you uncomment the code" - in a manner of speaking,

Re: Request for help with removing sequence numbers from PDS members

So, it's the invocation of EDIT that's causing the error. If you add an ISPLOG DD (RECFM VBA, LRECL 125) do you get more info? Otherwise we're into adding some say statements in to see what , and are set to, and wrapping the whole thing in CONTROL ERRORS so we can see what we get back in

Re: Request for help with removing sequence numbers from PDS members

Sean, If your shop has File-manager , the following JCL will give you the desired results //STEP0100 EXEC PGM=FILEMGR //SYSPRINT DD SYSOUT=* //PDS DD DISP=SHR,DSN=Your.PDS/PDSE.to.remove.seqnum //SYSINDD * $$FILEM FCH INPUT=PDS C P'=' ' ' 73 80 /* Thanks, Kolusu

Re: Ibm macro instructions code clarification

Without a little more info (i.e. what product) its kinda hard to help. BUT, having said that, FDBWD usually means FDB WORD 00141300 = the value of FDBWD FDBK2 ... there should be some data here. FDBK2 is normally some type of error code. Joe On Tue, Jan 12, 2021 at 12:55 AM Jake Anderson

Re: Request for help with removing sequence numbers from PDS members

Actually, I think it does. The MACRO parameter should have the name of the calling exec - the other parms have values as I would expect. Can you add a trace ir right at the top, it should show what the parse source is returning; you might instead add a say me .. The parse line should say:

Re: Request for help with removing sequence numbers from PDS members

The 'parse source . . me .' modification cracked the problem, Andy - many thanks! I see now from my very earliest version of the REXX, I had missed out the the space between the placeholders for the first two tokens That led me into a can of worms that eventually resulted in me removing the '. .

Re: Request for help with removing sequence numbers from PDS members

Hi Andy The ISPLOG output doesn't give anything useful, unfortunately. Time*** ISPF transaction log *** 07:08 Start of ISPF Log - - - - Session # 1 07:08 TSO - Command - - STRIPNOS 07:08 * Dialog Error *

STCK and epoch time

How exactly STCK (not STCKE) stores the time? I took the value (8 bytes) and converted it to decimal 10 characters. I expect it to be the same as the EPOCH time returned by USS time call. However the returned value is July 29, 2019 (have a time from yesterday). I know there is a macro to do it,

Re: STCK and epoch time

https://www.mail-archive.com/search?l=ibm-main@listserv.ua.edu=subject:%22Re%5C%3A+Converting+STCK%5C%28tod%5C%29+to+readable+format%22=newest=1 On Tue, Jan 12, 2021 at 9:37 AM ITschak Mugzach wrote: > > How exactly STCK (not STCKE) stores the time? I took the value (8 bytes) > and converted it

Merging multiple records using DFSORT

I'm currently using this * Merge the LW file * * These sort commands can handle both the old, it's left unchanged, as * well as the new, records are merged, LW output file. *** OPTION COPY INREC

Re: Ibm macro instructions code clarification

Apologies for giving a minimal information This is a SNA application where user use to connect Database and they receive FDBK2 00 This is the only information I have from the log and I have raised a case with Product support for further investigation and meanwhile just curious about these

Re: Request for help with removing sequence numbers from PDS members

ISREDIT is only valid for an edit macro. You need on script to invoke EDIT and a second script running as an IMACRO for the edit. If they are in SYSPROC then you need to start the first comment with REXX. /* Outer script */ parse upper arg dataset "CONTROL ERRORS RETURN" 'EDIT

Re: STCK and epoch time

The TOD clock is just a counter; what you get out of it depends on what you put into it. There is a convention in PoOps, but if you want the correct time and date it is much easier to use system services than to do the adjustments yourself. MVS does not use the same epoch as Eunix. Unix System

Re: Request for help with removing sequence numbers from PDS members

I have a REXX called ALLMEM, it gets the member list and calls an edit macro. I usually run it from 3.4. I'll post it here when I get my system going. On Wed, Jan 13, 2021 at 5:00 AM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 12 Jan 2021 13:46:07 -0400,

Re: STCK and epoch time

On Tue, 12 Jan 2021 16:30:52 +, Seymour J Metz wrote: >The TOD clock is just a counter; what you get out of it depends on what you >put into it. There is a convention in PoOps, but if you want the correct time >and date it is much easier to use system services than to do the adjustments

Re: Request for help with removing sequence numbers from PDS members

On Tue, 12 Jan 2021 13:46:07 -0400, Clark Morris wrote: >> >>And a general note: when using ISPF edit to remove sequence numbers from a >>(large) number of (large) members, you might need to cater for the fact that >>a >>PDS might need to be compressed at some stage in the middle of your

Re: STCK and epoch time

Nit: the code would be more readable with s hexadecimal constant for TOD. 70 * 3600 * 24 * 365 doesn't account for leap years. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on

Re: STCK and epoch time

Paul, So if I ignore leap seconds, Can I just divide the number by 409600 and subtruct 1.1.1970-1.1.1900? *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**:

Re: STCK and epoch time

409600 will give you units of 10 ms. Is that really what you want? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Itschak Mugzach

Re: STCK and epoch time

This is the STCK value: D91B6D3EF6430440 (I have it in hex in variable TOD) Converted to decimal : 15644217847788536896 Actual dat eof run is : Yesterday the code: /* rexx */ NUMERIC DIGITS 20 RC = SYSCALLS('ON') ADDRESS SYSCALL 'TIME' Say 'Current date is' retval TOD = 'R _

Re: STCK and epoch time

On Tue, 12 Jan 2021 19:19:01 +0200, Itschak Mugzach wrote: > >So if I ignore leap seconds, Can I just divide the number by 409600 and >subtruct 1.1.1970-1.1.1900? > Here's some code I wrote. The input data are the list of leap seconds in PoOp. Restriction: Presumes a system such as Linux

Re: STCK and epoch time

Tx Charles. I tested that there already. My rexx returns a different time. I noticed that they only use the first four bytes. The code snip I gave is from the TOD IPCS rexx. Anyway, it will be an assembler, but I still wonder why I get wrong numbers. ITschak *| **Itschak Mugzach | Director |

Re: STCK and epoch time

On Tue, 12 Jan 2021 19:19:01 +0200, Itschak Mugzach wrote: > >So if I ignore leap seconds, Can I just divide the number by 409600 and > 409600? >subtruct 1.1.1970-1.1.1900? > Are you doing it the hard way? Borrowing from seconds to minutes, minutes to hours, hours to days, days to months

Re: Code to verify LOGON password

W dniu 12.01.2021 o 06:42, Timothy Sipples pisze: Radoslaw Skorupka wrote: That's what we call brute force attack. There is no way to protect against it ...or maybe there are some things to help. 1. Do not give your RACF db to hackers. Never. 2. Enforce periodic password change. 3. Use KDFAES.

Re: Request for help with removing sequence numbers from PDS members

Whilst this basically true, you can have the same REXX invoked as a macro using the technique I used. Wrapping ISREDIT MACRO in CONTROL ERRORS allows you to get the RC20 if it's not running under Edit (and obviously any other major reasons) , this enabling you to determine which path through the

Re: Request for help with removing sequence numbers from PDS members

On Tue, 12 Jan 2021 18:41:54 +, Robert Prins wrote: > >... the advantage of keeping things together, like the PL/I RFE I've >very recently entered, >. >Feel free to vote for it, although I already expect it to be

Re: STCK and epoch time

http://www.longpelaexpertise.com/toolsTOD.php sez TOD: (STCK): x" D91B6D3E F6430440 " UTC Date and Time (Date + HH:MM:SS): 11-Jan-2021 21:25:22 UNIX Date/Time: 1610400322 Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of

Re: Request for help with removing sequence numbers from PDS members

On 2021-01-12 16:20, Seymour J Metz wrote: ISREDIT is only valid for an edit macro. You need on script to invoke EDIT and a second script running as an IMACRO for the edit. If they are in SYSPROC then you need to start the first comment with REXX. /* Outer script */ parse upper arg

Re: STCK and epoch time

As @Shmuel says, it depends on how the clock is set. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Itschak Mugzach Sent: Tuesday, January 12, 2021 9:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: STCK and epoch time

Re: Request for help with removing sequence numbers from PDS members

Whoops! Insert 'MACRO' after address ISREDIT. Also, you might want code to loop over all members of a PDS. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Seymour J

Re: Request for help with removing sequence numbers from PDS members

On Tue, 12 Jan 2021 16:20:17 +, Seymour J Metz wrote: >ISREDIT is only valid for an edit macro. You need on script to invoke EDIT and >a second script running as an IMACRO for the edit. If they are in SYSPROC then >you need to start the first comment with REXX. > Is the initial command

Re: Request for help with removing sequence numbers from PDS members

In either case, address ISPEXEC at the beginning wouldn't hurt. I noticed the missing macro after I posted it. This is Q code for a single member; if I had to do it for production I'd make it more general. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

Re: STCK and epoch time

True, but the difference may be within 24 hours. I get 21 days late *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522

Re: Code to verify LOGON password

W dniu 11.01.2021 o 17:44, Charles Mills pisze: https://en.wikipedia.org/wiki/John_the_Ripper There is a downloadable plugin for RACF -- old RACF hashing only, I *think*. @R.S. writes 1. Do not give your RACF db to hackers. Never. No one "gives" their RACF DB to anyone (I would hope). The

Re: Request for help with removing sequence numbers from PDS members

[Default] On 12 Jan 2021 08:42:24 -0800, in bit.listserv.ibm-main robert.ah.pr...@gmail.com (Robert Prins) wrote: >>snip > >And a general note: when using ISPF edit to remove sequence numbers from a >(large) number of (large) members, you might need to cater for the fact that a >PDS might need

Re: Compile error and also possible library bug with Metal/C metal.h

Another problem you have is you're not calling __cinit() [1] to initialize the Metal/C environment so the call to malloc() will fail as no heap has been created. You really must *always* check malloc() even in a test driver. [1]

Re: STCK and epoch time

Request for information. To convert from STCK format to Unix time, what constants would you subtract from the STCK value for the same origin, then divide by what constant for the same time unit? Or divide / subtract if easier. On Tue, Jan 12, 2021 at 5:09 PM Paul Gilmartin

Re: STCK and epoch time

On Tue, 12 Jan 2021 22:53:02 +0200, Itschak Mugzach wrote:. > >I tested that there already. My rexx returns a different time. I noticed >that they only use the first four bytes. The code snip I gave is from the >TOD IPCS rexx. > Regina gives me: 502 $ date Tue Jan 12 15:59:30 MST 2021 503 $ rxx

Re: STCK and epoch time

On Tue, 12 Jan 2021 17:24:52 -0600, Mike Schwab wrote: >Request for information. >To convert from STCK format to Unix time, what constants would you >subtract from the STCK value for the same origin, then divide by what >constant for the same time unit? Or divide / subtract if easier. > An

Re: STCK and epoch time

You can use IPCS LTOD stck-value to check that your calculation is correct George Kozakos z/OS Software Service, Level 2 Supervisor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: STCK and epoch time

On Tue, 12 Jan 2021 12:34:20 -0800, Charles Mills wrote: >http://www.longpelaexpertise.com/toolsTOD.php sez > >TOD: (STCK): x" D91B6D3E F6430440 " >UTC Date and Time (Date + HH:MM:SS): 11-Jan-2021 21:25:22 >UNIX Date/Time: 1610400322 > Some consequence of this impelled me to look for CVTLSO: