I was the NDM guy 20 years ago at Medical Mutual of Ohio. Before IBM bought them. We used to pay 20k a year for support. IBM raised it to 100k. So management dropped support and we went unsupported for 10 years.
Sent from Yahoo Mail for iPhone On Friday, July 18, 2025, 4:41 PM, Steve Thompson <[email protected]> wrote: History: Years ago when IBM acquired Sterling Commerce, were were in the process of migrating from Endevor to SCLM (at least Connect:Direct was making that change). Then we had to do some extraordinary rapid work: We had just a few weeks to Blue Wash C:D and the problem was, I had warned management this was coming and they blew me off. So when Management called the meeting on what our prefix had to become (which I had been asking for, for a few weeks knowing what was coming), the only way to get us to DGA as the 3 char prefix of all components in the short time we had was to ALIAS all of our code with those NEW names, keep an XREF of OLD/NEW, set up the new SMP/E environment using the Blue Washed names, fixing the different elements to point to an alias (the original names), to get done by the dead line and ship a "Blue washed" release. (You try to fix all the macros to have a new name, and then internally use the new names and all of the DSECTs to have the new name.... Yeah, all the ISPF panels, etc. etc). The question was asked by management how long this would take. There were 5 of us to do this work in our spare time. This would have meant NO fixes could be done, no "put" tapes could be put out. No work on current development projects until this was completed... I told them this was going to take, if I remember correctly, 5 man years. And it would be full time. No one argued with me they were numb. Then after about a year or so, IBM spun off the C:D group and all their software to another company. And I don't think, but would be surprised, if no one is left who was part of C:D back when I was working there. So I've been wondering what they were doing for L1/2 support since all those people retired or got laid off. Knowing all this, you may have some fall out with some of the members in the libraries if the developers didn't have to clean up the directory entries because of being moved to yet another source control system. And I understand the developers and product was spun off to yet another company. Regards, Steve Thompson On 7/18/2025 3:47 PM, Chalk, Shelia wrote: > Thank you very much for helping me with this. > > Thanks > > Shelia Chalk > Mainframe System Programmer > [email protected] > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf Of > David Spiegel > Sent: Friday, July 18, 2025 2:45 PM > To: [email protected] > Subject: [EXT] Re: [EXT] Re: [EXT] Re: [EXT] Re: [EXT] Re: [EXT] Re: z/os 3.1 > SCLM > > Please Note: This email is from an [EXTERNAL] sender. Do not click on links > or attachments unless you expect them from the sender and know the content is > safe. Please contact the Service Desk if you have any concerns regarding this > message. > > > > Hi Shelia, > You can turn it off by using ISPF 3.5 and change each member to Non-SCLM. > > Regards, > David > > On 2025-07-18 15:37, Chalk, Shelia wrote: >> I was trying to figure that out. I really don't want to use sclm. I didn't >> know about sclm until today. How can I turn it off? I ask ibm but no answer. >> >> Our theory is that we order the z/os 3.1 and connect direct 6.4 was order it >> came it with sclm. We are guessing. >> >> So, we are going to turn off in the ispf >> SCLM_WARNING_LEVEL = NONE >> >> Do you recommend this ? >> >> Thanks >> >> Shelia Chalk >> Mainframe System Programmer >> [email protected] >> >> -----Original Message----- >> From: IBM Mainframe Discussion List <[email protected]> On >> Behalf Of David Spiegel >> Sent: Friday, July 18, 2025 2:03 PM >> To: [email protected] >> Subject: [EXT] Re: [EXT] Re: [EXT] Re: [EXT] Re: [EXT] Re: z/os 3.1 >> SCLM >> >> Please Note: This email is from an [EXTERNAL] sender. Do not click on links >> or attachments unless you expect them from the sender and know the content >> is safe. Please contact the Service Desk if you have any concerns regarding >> this message. >> >> >> >> Hi Shelia, >> My understanding is that even though SCLM is supplied with ISPF, it is not >> supported. >> >> Regards, >> David >> >> On 2025-07-18 14:31, Chalk, Shelia wrote: >>> David, >>> These people are trying install a new release of connect direct on z/os 3.1 >>> lpar and we are getting the sclm message. >>> I am trying to figure out what you meant by Why are you using unsupported >>> software for Source Code Management? >>> >>> Can you help me understand? >>> >>> Thanks >>> >>> >>> Shelia Chalk >>> Mainframe System Programmer >>> [email protected] >>> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List <[email protected]> On >>> Behalf Of David Spiegel >>> Sent: Friday, July 18, 2025 12:46 PM >>> To: [email protected] >>> Subject: [EXT] Re: [EXT] Re: [EXT] Re: [EXT] Re: z/os 3.1 SCLM >>> >>> Please Note: This email is from an [EXTERNAL] sender. Do not click on links >>> or attachments unless you expect them from the sender and know the content >>> is safe. Please contact the Service Desk if you have any concerns regarding >>> this message. >>> >>> >>> >>> Hi Shelia, >>> That is the difference between your 2.4 and 3.1 system. >>> Why are you using unsupported software for Source Code Management? >>> >>> Regards, >>> David >>> >>> On 2025-07-18 13:25, Chalk, Shelia wrote: >>>> No >>>> >>>> >>>> Shelia Chalk >>>> Mainframe System Programmer >>>> [email protected] >>>> >>>> -----Original Message----- >>>> From: IBM Mainframe Discussion List <[email protected]> On >>>> Behalf Of David Spiegel >>>> Sent: Friday, July 18, 2025 12:25 PM >>>> To: [email protected] >>>> Subject: [EXT] Re: [EXT] Re: [EXT] Re: z/os 3.1 SCLM >>>> >>>> Please Note: This email is from an [EXTERNAL] sender. Do not click on >>>> links or attachments unless you expect them from the sender and know the >>>> content is safe. Please contact the Service Desk if you have any concerns >>>> regarding this message. >>>> >>>> >>>> >>>> Hi Shelia, >>>> Is there a SCLM Project involving Connect:Direct on 2.4? >>>> >>>> Regards, >>>> David >>>> >>>> On 2025-07-18 13:17, Chalk, Shelia wrote: >>>>> Yes >>>>> >>>>> >>>>> Shelia Chalk >>>>> Mainframe System Programmer >>>>> [email protected] >>>>> >>>>> -----Original Message----- >>>>> From: IBM Mainframe Discussion List <[email protected]> On >>>>> Behalf Of David Spiegel >>>>> Sent: Friday, July 18, 2025 12:15 PM >>>>> To: [email protected] >>>>> Subject: [EXT] Re: [EXT] Re: z/os 3.1 SCLM >>>>> >>>>> Please Note: This email is from an [EXTERNAL] sender. Do not click on >>>>> links or attachments unless you expect them from the sender and know the >>>>> content is safe. Please contact the Service Desk if you have any concerns >>>>> regarding this message. >>>>> >>>>> >>>>> >>>>> Hi Shelia, >>>>> Is there a z/OS 3.1 SCLM Project involving DGA (Connect:Direct)? >>>>> >>>>> Regards, >>>>> David >>>>> >>>>> On 2025-07-18 13:02, Chalk, Shelia wrote: >>>>>> Thanks for reaching out. But I have z/os 2.4 lpar and when create a new >>>>>> dataset I don't get the sclm message. >>>>>> Then I have a z/os 3.1 lpar and when we create a new dataset, I get the >>>>>> sclm message. >>>>>> >>>>>> I can't figure out where the difference is? I have looked at the >>>>>> SCLM_WARNING_LEVEL default is warn in all z/os 2.4,2.5 and 3.1. I can >>>>>> update the ispcfigu to turn warn to none. >>>>>> But it is not that way on z/os 2.4. >>>>>> >>>>>> Hopefully, this makes sense. >>>>>> >>>>>> Thanks for your help again. >>>>>> >>>>>> Shelia Chalk >>>>>> Mainframe System Programmer >>>>>> [email protected] >>>>>> >>>>>> -----Original Message----- >>>>>> From: IBM Mainframe Discussion List <[email protected]> On >>>>>> Behalf Of David Spiegel >>>>>> Sent: Friday, July 18, 2025 11:26 AM >>>>>> To: [email protected] >>>>>> Subject: [EXT] Re: z/os 3.1 SCLM >>>>>> >>>>>> Please Note: This email is from an [EXTERNAL] sender. Do not click on >>>>>> links or attachments unless you expect them from the sender and know the >>>>>> content is safe. Please contact the Service Desk if you have any >>>>>> concerns regarding this message. >>>>>> >>>>>> >>>>>> >>>>>> Hi Shelia, >>>>>> I think that you can change this by modifying (or deleting) the ISPF >>>>>> Stats for the member (or zapping Byte 3). >>>>>> Please see: >>>>>> ISPF statistics entry in a PDS directory >>>>>> >>>>>> z/OS ISPF Dialog Developer's Guide and Reference >>>>>> SC19-3619-00 >>>>>> >>>>>> A valid ISPF directory can consist of fifteen halfwords of user data >>>>>> with bytes 28-30 blank, or twenty half words of user data with bit 3 of >>>>>> byte 3 set on. Shown here is the format of the information that ISPF >>>>>> writes to the PDS directory to maintain statistics for a member. If you >>>>>> suspect the statistics data has been corrupted, you can compare the >>>>>> existing entry against these formats to help in problem determination. >>>>>> >>>>>> *Byte* >>>>>> *Description and Format* >>>>>> 1 >>>>>> Version number, in hexadecimal format. Value is >>>>>>betweenX'01'andX'99'. >>>>>> 2 >>>>>> Modification level, in hexadecimal format. Value is >>>>>> betweenX'00'andX'99'. >>>>>> 3 >>>>>> Flags: >>>>>> >>>>>> Bit 1 >>>>>> SCLM indicator. SCLM uses this to determine whether the >>>>>>member >>>>>> and any related SCLM information are still in sync. >>>>>> >>>>>> * ON means the member was last edited by SCLM, the >>>>>>Software >>>>>> Configuration and Library Manager. >>>>>> * OFF means the member was somehow processed outside SCLM. >>>>>> >>>>>> One way to do this is to start 3.5 and change the SCLM setting to >>>>>> Non-SCLM. >>>>>> >>>>>> Regards, >>>>>> David >>>>>> >>>>>> On 2025-07-18 11:34, Chalk, Shelia wrote: >>>>>>> On Z/OS 3.1 I am getting message on some members in a dataset that I >>>>>>> trying to edit. >>>>>>> Happens on some datasets and not others. >>>>>>> >>>>>>> EDIT DGA.SDGACNTL(DGACBACK) - 01.04 >>>>>>> SCLM warning >>>>>>> Command ===> Scroll ===> PAGE >>>>>>> ****** ***************************** Top of Data >>>>>>> *********************** ==MSG> -CAUTION- Saving this member will >>>>>>> invalidate the SCLM accounting ==MSG> information. Refer to the edit >>>>>>> tutorial for further details. >>>>>>> ==MSG> -CAUTION- Profile changed to CAPS OFF (from CAPS ON) >>>>>>> because data ==MSG> contains lower case characters. >>>>>>> ==MSG> -Warning- The UNDO command is not available until you >>>>>>> change ==MSG> your edit profile using the command RECOVERY ON. >>>>>>> >>>>>>> Can anyone tell me how to turn this off or how to fix this? >>>>>>> >>>>>>> Thanks >>>>>>> Shelia Chalk >>>>>>> Mainframe System Programmer >>>>>>> [email protected] >>>>>>> >>>>>>> ======================================= This email, and any files >>>>>>> transmitted with it, is confidential and intended solely for the use of >>>>>>> the individual or entity to which it is addressed. If you have received >>>>>>> this email in error, please notify the system manager. This message >>>>>>> contains confidential information and is intended only for the >>>>>>> individual named. If you are not the named addressee, you should not >>>>>>> disseminate, distribute or copy this e-mail. Please notify the sender >>>>>>> immediately by e-mail if you have received this message by mistake and >>>>>>> delete this e-mail from your system. If you are not the intended >>>>>>> recipient, you are notified that disclosing, copying, distributing or >>>>>>> taking any action in reliance on the contents of this information is >>>>>>> strictly prohibited. >>>>>>> >>>>>>> ----------------------------------------------------------------- >>>>>>> - >>>>>>> - >>>>>>> - >>>>>>> - >>>>>>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>>>>>> send email [email protected] with the message: INFO >>>>>>> IBM-MAIN >>>>>> ------------------------------------------------------------------ >>>>>> - >>>>>> - >>>>>> - >>>>>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>>>>> send email to [email protected] with the message: INFO >>>>>> IBM-MAIN ======================================= This email, and any >>>>>> files transmitted with it, is confidential and intended solely for the >>>>>> use of the individual or entity to which it is addressed. If you have >>>>>> received this email in error, please notify the system manager. This >>>>>> message contains confidential information and is intended only for the >>>>>> individual named. If you are not the named addressee, you should not >>>>>> disseminate, distribute or copy this e-mail. Please notify the sender >>>>>> immediately by e-mail if you have received this message by mistake and >>>>>> delete this e-mail from your system. If you are not the intended >>>>>> recipient, you are notified that disclosing, copying, distributing or >>>>>> taking any action in reliance on the contents of this information is >>>>>> strictly prohibited. >>>>>> >>>>>> ------------------------------------------------------------------ >>>>>> - >>>>>> - >>>>>> - >>>>>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>>>>> send email to [email protected] with the message: INFO >>>>>> IBM-MAIN >>>>> ------------------------------------------------------------------- >>>>> - >>>>> - >>>>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>>>> send email to [email protected] with the message: INFO >>>>> IBM-MAIN ======================================= This email, and any >>>>> files transmitted with it, is confidential and intended solely for the >>>>> use of the individual or entity to which it is addressed. If you have >>>>> received this email in error, please notify the system manager. This >>>>> message contains confidential information and is intended only for the >>>>> individual named. If you are not the named addressee, you should not >>>>> disseminate, distribute or copy this e-mail. Please notify the sender >>>>> immediately by e-mail if you have received this message by mistake and >>>>> delete this e-mail from your system. If you are not the intended >>>>> recipient, you are notified that disclosing, copying, distributing or >>>>> taking any action in reliance on the contents of this information is >>>>> strictly prohibited. >>>>> >>>>> ------------------------------------------------------------------- >>>>> - >>>>> - >>>>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>>>> send email to [email protected] with the message: INFO >>>>> IBM-MAIN >>>> -------------------------------------------------------------------- >>>> - >>>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected] with the message: INFO >>>> IBM-MAIN ======================================= This email, and any files >>>> transmitted with it, is confidential and intended solely for the use of >>>> the individual or entity to which it is addressed. If you have received >>>> this email in error, please notify the system manager. This message >>>> contains confidential information and is intended only for the individual >>>> named. If you are not the named addressee, you should not disseminate, >>>> distribute or copy this e-mail. Please notify the sender immediately by >>>> e-mail if you have received this message by mistake and delete this e-mail >>>> from your system. If you are not the intended recipient, you are notified >>>> that disclosing, copying, distributing or taking any action in reliance on >>>> the contents of this information is strictly prohibited. >>>> >>>> -------------------------------------------------------------------- >>>> - >>>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected] with the message: INFO >>>> IBM-MAIN >>> --------------------------------------------------------------------- >>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO >>> IBM-MAIN ======================================= This email, and any files >>> transmitted with it, is confidential and intended solely for the use of the >>> individual or entity to which it is addressed. If you have received this >>> email in error, please notify the system manager. This message contains >>> confidential information and is intended only for the individual named. If >>> you are not the named addressee, you should not disseminate, distribute or >>> copy this e-mail. Please notify the sender immediately by e-mail if you >>> have received this message by mistake and delete this e-mail from your >>> system. If you are not the intended recipient, you are notified that >>> disclosing, copying, distributing or taking any action in reliance on the >>> contents of this information is strictly prohibited. >>> >>> --------------------------------------------------------------------- >>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO >>> IBM-MAIN >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to [email protected] with the message: INFO IBM-MAIN >> ======================================= This email, and any files >> transmitted with it, is confidential and intended solely for the use of the >> individual or entity to which it is addressed. If you have received this >> email in error, please notify the system manager. This message contains >> confidential information and is intended only for the individual named. If >> you are not the named addressee, you should not disseminate, distribute or >> copy this e-mail. Please notify the sender immediately by e-mail if you have >> received this message by mistake and delete this e-mail from your system. If >> you are not the intended recipient, you are notified that disclosing, >> copying, distributing or taking any action in reliance on the contents of >> this information is strictly prohibited. >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > ======================================= This email, and any files transmitted > with it, is confidential and intended solely for the use of the individual or > entity to which it is addressed. If you have received this email in error, > please notify the system manager. This message contains confidential > information and is intended only for the individual named. If you are not the > named addressee, you should not disseminate, distribute or copy this e-mail. > Please notify the sender immediately by e-mail if you have received this > message by mistake and delete this e-mail from your system. If you are not > the intended recipient, you are notified that disclosing, copying, > distributing or taking any action in reliance on the contents of this > information is strictly prohibited. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Regards, Steve Thompson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
