Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS

2024-03-20 Thread Timothy Sipples
The “night light” CICS program can be quite simple and written in any language — in REXX, for example. You probably ought to include a link to the replacement application and help desk details. For example: REPLACEMENT APPLICATION NOTICE [Application ABC] replaced [Application XYZ] on March 8,

Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS

2024-03-20 Thread Paul Feller
Tom, I think whoever is responsible for this project is going to have to come up with some help around the CICS stuff. It sounds like Solve is similar to CL/Supersession. I don't think the Solve software will help you much in this situation. Technically the CICS program does not need a MAP

Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS

2024-03-20 Thread Mike Schwab
Here is a set of CICS transactions to perform DogeCoin transactions via CICS. The first screen could be simplified to be display only, https://github.com/mainframed/DOGECICS On Wed, Mar 20, 2024 at 4:01 PM Tom Longfellow <03e29b607131-dmarc-requ...@listserv.ua.edu> wrote: > > Paul > > The

Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS

2024-03-20 Thread roscoe5
It’s been decades since I wrote my last CICS application, but if I understand your desire, you want feedback better than an IBM error. If transaction ABCD previously pointed to a program (with maps and everything associated) it’s trivial to create a page that says “Nobody home, go away.” or

Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS

2024-03-20 Thread Tom Longfellow
Paul The answer to your question is BOTH - Individual apps are being yanked before the eventual complete shutdown of everything the region does. Our internal thoughts parallel your ideas for CICS. One of the hurdles is that since the mainframe is marked for death, we have no real access to

Re: FTP problem

2024-03-20 Thread Phil Smith III
Colin Paice wrote: >It may be interaction with _BPXK_AUTOCVT environment variable, and >possibly the FILETAG Hmm. _BPXK_AUTOCVT is ON; setting it to OFF means that a text file tagged as ISO8859-1 now displays as garbage, which makes sense. IBM-1047 and untagged files display OK. (It also breaks

Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS

2024-03-20 Thread Paul Feller
Hi Tom.. Let me start by saying I don't know anything about Solve. Now to my question. Are you talking about individual CICS transactions going away or are you talking about the whole CICS region going away? If you are talking about individual CICS transactions then you could handle things

Re: DFSORT and IPL Date

2024-03-20 Thread Sri Hari Kolusu
>> What I am trying to achieve is simple. I want to select, using DCOLLECT TYPE >> D records, files that have been created after the last IPL and ten days >> before today: Jack, As I showed you earlier , you can use the SDSF REXX interface and get the IPLINFO and we can parse to create a

Re: Rexx numeric digits and scientific notation question

2024-03-20 Thread Oscar
El 2024-03-19 02:40, David Crayford escribió: On 19 Mar 2024, at 9:08 am, Andrew Rowley wrote: On 19/03/2024 11:05 am, David Crayford wrote: If you’re care so much about Java catching errors at compile time then why don’t you use Kotlin instead? NPE’s are one of the most common form of

Ideas for less-distruptive disruptions - Netmaster:Solve and CICS

2024-03-20 Thread Tom Longfellow
Our mainframe is scheduled for termination.As such, bits and pieces are being turned off. Management edicts wants "no sudden surprise screens and error messages" when a function is killed. A "landing screen" has been proposed that would do the required hand holding with messages like

Re: DFSORT and IPL Date

2024-03-20 Thread Jack Zukt
Hi Kolusu, What I am trying to achieve is simple. I want to select, using DCOLLECT TYPE D records, files that have been created after the last IPL and ten days before today: INCLUDE COND=(DCURCTYP,EQ,DCUDATAT,AND, * Type = Data type DCDCREDT,LT,DATE3P-10,&, * Created < curr date

Re: TSO ALLOC with/wo unit

2024-03-20 Thread David Spiegel
Hi Leonard, In the case of an uncataloged Dataset, it would be necessary. Regards, David On 2024-03-20 04:44, Leonard D Woren wrote: Specifying VOLUME more or less always requires specification of UNIT. Ignoring SMS altering the historic behavior, there is a "default unitname" associated with

Re: TSO ALLOC with/wo unit

2024-03-20 Thread David Spiegel
HI Mike, 3390 (and SYSALLDA) do not depend upon HCD. "I/O gen"? -- There has not been one since MVS/ESA V5. (MVS/ESA 4.3 was the last one to support it.) Regards, David On 2024-03-20 04:52, Mike Schwab wrote: UNIT is defined in the I/O gen and is customized by each site. 3390, SYSDA, etc

Re: DFSORT and IPL Date

2024-03-20 Thread Scott Barry
Okay, yes, these more-recent z/OS JCL days that's true - JCL SYMBOLs are now directly accessible in SYSIN DD *,SYMBOLS= -- but not indirectly when the SYSIN is not instream, so the JP"" method as a PARM= continues to be viable to bridge / pass symbolic data and have it be resolved within

Re: DFSORT and IPL Date

2024-03-20 Thread Sri Hari Kolusu
>> Is there a way to make SORT date comparisons referencing the IPL date? I >> have not been able to find anything on the manual. Jack, DFSORT does not have direct access to IPL info. It can access system symbols but there is no system symbol defined for LAST IPL date (AFAIK). So as others

Re: DFSORT and IPL Date

2024-03-20 Thread Jack Zukt
The use of a JP variable is an interesting possibility. It does not solve the problem but it will provide an interim solution that can be easily maintained. Thank you Regards Jack On Wed, 20 Mar 2024 at 14:42, Scott Barry wrote: > One option is to harvest the /D IPLINFO information at IPL-time

Re: DFSORT and IPL Date

2024-03-20 Thread Scott Barry
One option is to harvest the /D IPLINFO information at IPL-time (maybe using an automated-SUBMIT batch-job DFSORT / ICETOOL, or SAS, or REXX, etc.), parse and set a site-specific SYMBOL - then you can use it in one of various methods in a batch DFSORT job via an expected JCL INCLUDE MEMBER=.

Re: DFSORT and IPL Date

2024-03-20 Thread Massimo Biancucci
Jack, AFAIK SORT tools have no such capability. As Scott suggested you need to write yourself something or, only for instance, if you installed Mark Zelden IPLINFO tool you can invoke it and extract the information from its output. Regards Max Il giorno mer 20 mar 2024 alle ore 14:41 Jack Zukt

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Itschak Mugzach
I think it is the data in the tso segment. *| **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 986404 **|* *Skype**:

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Michael Babcock
SMS versus non-SMS? Esoterics? On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach < 05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote: > I have a program in Rexx that allocates a dataset using dsname and volume > serial (1) . it works well in my shop but requires a unit type (2) in > another

Re: DFSORT and IPL Date

2024-03-20 Thread Jack Zukt
Hi Scott, Thank you for the suggestion. I am trying to build the JCL using only DFSORT capabilities. I was just wondering if maybe that particular capability would be available, as DFSORT as a wide range of date processing. An may be that if not yet, it would become available in the near future

Re: DFSORT and IPL Date

2024-03-20 Thread Scott Barry
Possibly a REXX process to capture/parse the output of a z/OS command /D IPLINFO. Scott Barry SBBTech LLC -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Lennie Bradshaw
For TSO allocations I think it depends what is specified in the UNIT parameter in your TSO RACF segment. If you have SYSALLDA specified then this will accept any DASD device. With a specification of SYSDA however, this will depend on the Eligible Device Table entries at the site. Lennie

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Itschak Mugzach
Tx. I forgot this one! *| **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 986404 **|* *Skype**: ItschakMugzach **|*

AW: [IBM-MAIN] TSO ALLOC with/wo unit

2024-03-20 Thread Beate Kawelke
SYSALLDA will also work - see https://www.ibm.com/docs/en/zos/2.5.0?topic=up-subparameter-definition-1 -Ursprüngliche Nachricht- Von: IBM Mainframe Discussion List Im Auftrag von Itschak Mugzach Gesendet: Mittwoch, 20. März 2024 09:54 An: IBM-MAIN@LISTSERV.UA.EDU Betreff: Re:

DFSORT and IPL Date

2024-03-20 Thread Jack Zukt
Hi, Is there a way to make SORT date comparisons referencing the IPL date? I have not been able to find anything on the manual. Regards Jack -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Itschak Mugzach
Agree, but it is common to use the devtype 3390. *| **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 986404 **|* *Skype**:

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Itschak Mugzach
Tx. I think the answer is in the volume operand (I marked it in red). The reason I use volume operand is that the source of the dataset information is APF, where the dataset does not have to be cataloged. If the volume value is not SMS, I allocate it with the volume information. otherwise I

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Mike Schwab
UNIT is defined in the I/O gen and is customized by each site. 3390, SYSDA, etc may or may not be present. On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach <05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote: > > I have a program in Rexx that allocates a dataset using dsname and volume >

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Leonard D Woren
Specifying VOLUME more or less always requires specification of UNIT.  Ignoring SMS altering the historic behavior, there is a "default unitname" associated with each userid.  For ALLOC VOL to work without UNIT, the VOL specified must be within the set of devices covered by that default

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Gadi Ben-Avi
I'm not sure. I wouldn't add volume and unit for an allocation for an existing dataset. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Itschak Mugzach Sent: יום ד 20 מרץ 2024 10:28 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: TSO ALLOC with/wo unit [You don't

Auto: Re: TSO ALLOC with/wo unit

2024-03-20 Thread Frederic Mancini
Je suis absent le 20 mars 2024. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Itschak Mugzach
GAdi, Does this rule apply to existing datasets? The allocation request was for existing datasets not new. *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**:

Re: TSO ALLOC with/wo unit

2024-03-20 Thread Gadi Ben-Avi
As far as I know, If you do not specify a UNIT Type, it will look for volumes that are STORAGE. If there aren't any, the allocation will fail. -Original Message- From: IBM Mainframe Discussion List On Behalf Of ITschak Mugzach Sent: יום ד 20 מרץ 2024 08:57 To: IBM-MAIN@LISTSERV.UA.EDU

TSO ALLOC with/wo unit

2024-03-20 Thread ITschak Mugzach
I have a program in Rexx that allocates a dataset using dsname and volume serial (1) . it works well in my shop but requires a unit type (2) in another shop. Actually the error is msg "IKJ56241I SPECIFIED UNIT IS UNDEFINED". Why does 1 work here and fails in another shop? 1. ALLOC F(XXX)