IBM Statement of Direction: Fibre Channel Endpoint Security

2024-04-23 Thread Timothy Sipples
I’d like to draw your attention to this new IBM Statement of Direction regarding IBM Fibre Channel Endpoint Security with FICON-attached devices: https://www.ibm.com/docs/en/announcements/statement-direction-1-qtr-2024 More information is available here:

Re: S0c4 creation

2024-04-23 Thread Tony Harminc
On Mon, 22 Apr 2024 at 09:50, Seymour J Metz wrote: > IBM promised to never use opcode 00, and that's what I use when I want > (E)SPIE in the skie. > But way back when (around the last S/370 PofO they said "The operation code 00, with a two-byte instruction format, and the set of sixteen 16-bit

Re: Commands via Rexx (Re: REXX vs other languages WAS: Rexx numeric digits and scientific notation question

2024-04-23 Thread Jeremy Nicoll
On Tue, 23 Apr 2024, at 11:25, Rony G. Flatscher wrote: > The nice thing is that Rexx allows different variants of string > concatenations and one is free to use what seems to be the > "easiest", the "safest". Personally I use blank concatenations > by default and abuttal or || only if there

Re: REXX vs other languages WAS: Rexx numeric digits and scientific notation question

2024-04-23 Thread Eric Rossman
I rather prefer the 'A '||B format because it makes it very clear that I'm doing string concatenation. I use the same construct in other languages. REXX C = 'A '||B Python and Java C = "A " + B Bash C = "A " C += B Etc. I don't know of any (normal) language where whitespace is important. I

Re: REXX vs other languages

2024-04-23 Thread Robin Vowels
On 2024-04-24 00:41, Paul Gilmartin wrote: On Tue, 23 Apr 2024 14:07:05 +, Schmitt, Michael wrote: Be sparse and elegant but not rococo. I prefer: 'A' B to (the equivalent): 'A ' || B The latter seems to cater to the expectations of PL/I or some other language. Catenation with

Re: REXX vs other languages WAS: Rexx numeric digits and scientific notation question

2024-04-23 Thread Paul Gilmartin
On Tue, 23 Apr 2024 14:07:05 +, Schmitt, Michael wrote: >You lost me when you say that rather than embrace the conventions, standards, >and features of the language I'm coding in (REXX), I should restrict it to the >limitations of other languages. > Did I say that? I was trying to take a

Re: dummy IDCAMS ALTER

2024-04-23 Thread Massimo Biancucci
Hi, I did a couple of tests. If the VSAM is allocated to CICS I receive a IDC3351I with reason 168 during the VERIFY. As far as I understand, ALTER with no parm does nothing but ensure the file is not allocated to any other user. Hope this helps. Max

Re: REXX vs other languages WAS: Rexx numeric digits and scientific notation question

2024-04-23 Thread Schmitt, Michael
You lost me when you say that rather than embrace the conventions, standards, and features of the language I'm coding in (REXX), I should restrict it to the limitations of other languages. The maxim is to assume that readers of your code are familiar with the language you're coding in, and

dummy IDCAMS ALTER

2024-04-23 Thread Radoslaw Skorupka
I have found a job with series of following commands: ALTER HLQ.SOME.VSAM.CLSTR ALTER HLQ.SOME.VSAM.CLSTR.* ALTER HLQ.YET.ANOTHER ALTER HLQ.YET.ANOTHER.* ... Q: what does it do? Another question: First step in the job is a series of VERIFY HLQ.SOME.VSAM commands. During the day the VSAM files

Commands via Rexx (Re: REXX vs other languages WAS: Rexx numeric digits and scientific notation question

2024-04-23 Thread Rony G. Flatscher
On 23.04.2024 05:03, Andrew Rowley wrote: On 23/04/2024 11:55 am, Paul Gilmartin wrote: On Tue, 23 Apr 2024 10:59:47 +1000, Andrew Rowley  wrote:     ... To me, it is much clearer to be explicit, including the concatenation, e.g. "DELETE " || foo That overkill is apt to confuse a POSIX shell