Re: can DIE routines invoke macro's using linkage=system

The documentation for each macro has a section labeled "Environment". Is there a particular macro for which you have read the documentation and you are unable to understand it? Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List"

PL/I support of vector instructions?

Has IBM announced an intention to support the vector instructions to allow more precision for FIXED DEC and FIXED BIN in PL/I? Are there other vendors that support greater precision? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

Re: REXX true/false (was Constant Identifiers)

Have you ever heard of PL/I? Much of the syntax of REXX derives from PL/I, and it has two different string types: CHARACTER and BIT. With regard to the built in functions, you are once again confusing the type of a variable with its contents. Would you argue that +1 in -1 are different data

Re: Ransoming a mainframe disk farm

kekronbekron wrote: >Thank you Tim, would you be able to share any info about #2 >here.. ? Yes, let's start with this important announcement: https://www.ibm.com/downloads/cas/US-ENUS220-037-CA/name/US-ENUS220-037-CA.PDF - - - - - - - - - - Timothy Sipples I.T. Architect Executive Digital Asset

Re: REXX true/false (was Constant Identifiers)

Y'all are dancing on the head of a pin. As Shmuel said, Rexx has one datatype, period. It has the DATATYPE function that can do some analysis on a variable's contents and tell you whether it's all numeric, hex, etc. That's basically it. Arguing about whether it's a "string" or a "character

Re: linker error c++ multithreaded program

hi Sam, Those symbols are not intended to be externalized, they are marked with visibility being hidden. Please check the setting of _LIBCPP_THREAD_ABI_VISIBILITY. If that doesn't help, could you please open a case with IBM support so we can help you better.

can DIE routines invoke macro's using linkage=system

thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: REXX true/false (was Constant Identifiers)

Don't bother. IBM will reply NAPWAD (not a problem, working as designed). ;-) On 08/09/2020 16:22, Paul Gilmartin wrote: > (cross-posting to IBM-Main and TSO-REXX) > On 2020-09-08, at 00:23:52, CM Poncelet wrote: >> A *character* string is either any string that has DATATYPE CHAR but not >>

Re: REXX true/false (was Constant Identifiers)

Mr Bridges,   1) The reason the program does not abend is it has a "SIGNAL ON SYNTAX NAME ERROR3" coded before the "IF TRUE THEN...", which traps the abend and resumes execution at label ERROR3.   2) I disagree with Mr Metz on the grounds that he argues that "everything in REXX is a character

Re: New listening port for ftp

You have to precede the parm with a "/" ... for LE-conforming programs the LE options appear on the JCL EXEC PARM='LEruntimeparm/programparms' ... so you code '/-PORT 9921' ... the joys of LE. Getting CEE error msg is a big hint :) On Wed, Sep 9, 2020 at 12:48 AM Roberto Halais wrote: >

PT Operator Needed

Hello All. Trident Services is seeking one mainframe computer operator. This is a part time position. Hours of work are Monday thru Friday from 9 pm to 2 am. We are looking for a minimum of 5 years’ experience and must know the following: 1.JES2 commands 2.

Re: REXX true/false (was Constant Identifiers)

Well, the distinction doesn't exist in REXX, but in PL/I there are bit strings and character strings, two different types. IMHO it would be clearer to consistently use the nomenclature character string. Possibly also a note that an implementation is free to use multiple internal

M3000 disks

Hello guys, Does anyone in Brazil who has some SSA Disks available for selling or donate? Thanks Dan Sent from my iPhone -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu

Re: REXX true/false (was Constant Identifiers)

Mr Poncelet, I'm interested in this example. Two questions: 1) Once TRUE is set to a '1'b in the last two sections, why does the program not abend when it encounters "IF TRUE THEN..."? Seems to me REXX should complain that TRUE is not 1 or 0. 2) From your preceding posts I got the impression

Re: REXX true/false (was Constant Identifiers)

(cross-posting to IBM-Main and TSO-REXX) On 2020-09-08, at 00:23:52, CM Poncelet wrote: > > A *character* string is either any string that has DATATYPE CHAR but not > DATATYPE NUM, or is *any* string (and it might as well then be called > 'anything string' instead of 'character string'). >

Re: Ransoming a mainframe disk farm

Thank you Tim, would you be able to share any info about #2 here.. ? - KB ‐‐‐ Original Message ‐‐‐ On Tuesday, September 8, 2020 10:27 AM, Timothy Sipples wrote: > Kekronbekron wrote: > > > Thinking about it ... it would be far simpler (than anti-ransomware > > capability in storage,

Re: New listening port for ftp

Thank you. So simple. It worked without the -. On Tue, Sep 8, 2020 at 10:52 AM Cieri, Anthony < 02d7f4ec1fff-dmarc-requ...@listserv.ua.edu> wrote: > > Try it without the '-'. I.E. //FTPS PROC > MODULE='FTPD',PARMS='Port 9921' > > > > -Original Message- > From: IBM

Re: New listening port for ftp

Try it without the '-'. I.E. //FTPS PROC MODULE='FTPD',PARMS='Port 9921' -Original Message- From: IBM Mainframe Discussion List On Behalf Of Roberto Halais Sent: Tuesday, September 08, 2020 10:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: New listening port for ftp [[

New listening port for ftp

Listers: I am implementing a second FTP stc and I want it to listen on port 9921. The FTPD proc listens on port 21 by default. I read somewhere that you could specify //FTPS EXEC PGM=FTPD,PARM=(-PORT 9921) but I get: CEE3611I The run-time option -PORT was an invalid run-time option. How do I

Re: REXX true/false (was Constant Identifiers)

> I agree that "it's all strings", but not that > "everything in REXX is a *character* string." That may be your opinion, but the opinion of Mike Cowlishaw is the one that matters. The DATATYPE() built in function does not identify the type of a variable; it classifies the type of a value, at

Re: Ransoming a mainframe disk farm

SafeGuarded Copy on IBM DS8000 On Fri, Sep 4, 2020, 21:50 Jesse 1 Robinson wrote: > It’s Friday, so don’t rag on me for venturing into IT fiction. No one has > hit us with this challenge (yet), but it could happen. > > Ransomware is much in the news these days. As unlikely as it might be, >

IBM Registration Server

I am attempting to register a new "IBM ID" and the registration server is not Returning the Verification E-Mail Steve Beaver st...@stevebeaver.com -- For IBM-MAIN subscribe / signoff /

Re: Ransoming a mainframe disk farm

Note that measures you instate to protect against a cotntingency you expect might also protect against contingencies you didn't anticipate; ransomware is not the only threat. ObChicago Backup early and often. Test your backups. Have remote backups far enough away that they are not affected by

Re: RFE 145094: No warning on "conflicting" use of "SEQ" keyword in SuperC

On Tue, 8 Sep 2020 13:03:28 +, Robert Prins wrote: >https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=145094 > >You use SuperC from the ISPF menu, see that there are no differences, copy the >generated JCL into a job, and suddenly there are differences, because you >forgot

Re: Synchronizing VTL VOLCAT and TMS

Thanks, I was hoping for a simpler way. But that, combined with CTTSYNC utility seems to have fixed the problem. I hope. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Fraser Sent: Tuesday, September 8, 2020 2:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject:

Re: [OT] Rabies [Was: Ransoming a mainframe disk farm]

It is an interesting note that the rabies protocol is post-exposure. You will get post-exposure treatments on Days 0, 3, 7, and 14. The treatment on day 0 consists of a globulin shot as well as the vaccine. The other three are vaccine only. Joe On Tue, Sep 8, 2020 at 5:46 AM Robert Prins

Re: Synchronizing VTL VOLCAT and TMS

IDCAMS CREATE VOLENT(NAME(Vvolser) LOC(library) MTYPE(mediatype) LIBNAME(libname) UATTR(scratch/private) On Tue, 8 Sep 2020 at 17:15, Gadi Ben-Avi wrote: > Hi, > We have the following situation: > Virtual volumes exist in the VTL (TS7760) using the correct category for a > specific LPAR. >

[OT] Rabies [Was: Ransoming a mainframe disk farm]

On 2020-09-08 10:15, R.S. wrote: W dniu 08.09.2020 o 14:09, Robert Prins pisze: On 2020-09-08 07:21, R.S. wrote: Well, I sustain my words: the only EFFECTIVE way is to prevent. All other ways are recipes what to do after failure happens, to minimize the impact. This resembles data loss

Re: Ransoming a mainframe disk farm

W dniu 08.09.2020 o 14:09, Robert Prins pisze: On 2020-09-08 07:21, R.S. wrote: Well, I sustain my words: the only EFFECTIVE way is to prevent. All other ways are recipes what to do after failure happens, to minimize the impact. This resembles data loss scenario. What to do when you lost

RFE 145094: No warning on "conflicting" use of "SEQ" keyword in SuperC

https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=145094 You use SuperC from the ISPF menu, see that there are no differences, copy the generated JCL into a job, and suddenly there are differences, because you forgot to zap the "SEQ" process option. It does no harm, but

Synchronizing VTL VOLCAT and TMS

Hi, We have the following situation: Virtual volumes exist in the VTL (TS7760) using the correct category for a specific LPAR. Some are in category 008F and some in 0082 The same volumes are defined in the TMS (Control-M/Tape in this case). The volumes are not defined in the VOLCAT. How can I

Re: Ransoming a mainframe disk farm

On 2020-09-08 07:21, R.S. wrote: Well, I sustain my words: the only EFFECTIVE way is to prevent. All other ways are recipes what to do after failure happens, to minimize the impact. This resembles data loss scenario. What to do when you lost your data? The answer is AVOID it. Use RAID

Re: Ransoming a mainframe disk farm

Well, I sustain my words: the only EFFECTIVE way is to prevent. All other ways are recipes what to do after failure happens, to minimize the impact. This resembles data loss scenario. What to do when you lost your data? The answer is AVOID it. Use RAID arrays, remote copies, backups, archive

Re: REXX true/false (was Constant Identifiers)

A *character* string is either any string that has DATATYPE CHAR but not DATATYPE NUM, or is *any* string (and it might as well then be called 'anything string' instead of 'character string'). Q: "What's your motivation and the motivation of the recondite examples you supplied (which I