> On 19 Jul 2023, at 12:44 pm, kekronbekron
> <02dee3fcae33-dmarc-requ...@listserv.ua.edu> wrote:
>
> The "gift" is not containers but container tech... layering.
> Just lifting and shifting distributed tech onto mainframe, with no
> consideration of the extreme complexities is very
The "gift" is not containers but container tech... layering.
Just lifting and shifting distributed tech onto mainframe, with no
consideration of the extreme complexities is very wasteful.
Container orchestration exists because some of those containers (or the hosts
they may run on) may have a
> On 19 Jul 2023, at 9:52 am, kekronbekron
> <02dee3fcae33-dmarc-requ...@listserv.ua.edu> wrote:
>
> Here's a dumb and bold prediction - the guts of RHEL (CoreOS) will be laid
> bare within zOS.
Nice idea, but I doubt it.
> USS becomes LSS. zOS native containers are actually normal
> On 19 Jul 2023, at 11:28 am, zMan wrote:
>
> Bill, Bill, Bill. Stick to stuff you know something about. IF quantum
> computers ever become realistically powerful, they will have VERY specific
> uses. They are not suited for general-purpose computing. Nobody even
> quantum-adjacent disputes
Bill, Bill, Bill. Stick to stuff you know something about. IF quantum
computers ever become realistically powerful, they will have VERY specific
uses. They are not suited for general-purpose computing. Nobody even
quantum-adjacent disputes that, as even the most cursory reading of the
research
Here's a dumb and bold prediction - the guts of RHEL (CoreOS) will be laid bare
within zOS.
USS becomes LSS. zOS native containers are actually normal containers that you
see in the linux world.
DSFS and zCX end up helping to blur the boundaries between zOS and LSS.
zOS is not going away. But we
Quantum computing is the future. And IBM is the leader.
https://www.forbes.com/sites/karlfreund/2023/06/14/ibm-achieves-breakthrough-in-quantum-computing/
Sent from Yahoo Mail for iPhone
On Tuesday, July 18, 2023, 8:47 PM, Jon Perryman wrote:
IBM RHEL announced it's move to closed source
IBM RHEL announced it's move to closed source (IBM RedHat Enterprise Linux).
With some changes, DB2, RACF and other z/OS products could run in Linux on z16
in one sysplexed Linux image. We know it's possible because IBM moved Unix and
TCP into z/OS. IBM RHEL said closed source would force
On Tue, 18 Jul 2023 18:58:54 +0300, Binyamin Dissen wrote:
>
>It is pure batch, which may have only the single task.
>
If it's pure batch, with only a single task, code STEPLIB in JCL.
If it's Assembler with multiple tasks, code TASKLIB in the ATTACH MACRO.
What environment prevents this?
>On
If I was using TSO in batch it would be quite easy. There are many parent
tasks available.
It is pure batch, which may have only the single task.
On Tue, 18 Jul 2023 10:53:23 -0500 "Lionel B. Dyck" wrote:
:>I'm assuming (and I know the danger of doing that) that you are using TSO in
:>batch
Hi Binyamin AMV"SH,
Please see CBT File 452 (and 797).
Regards,
David
On 2023-07-18 11:49, Binyamin Dissen wrote:
I am trying to do the equivalent of TSOLIB for BATCH, i.e., dynamically adding
loadlibs. I do not have spare parent tasks that I can hang a JLB DCB.
It appears that the system is
I'm assuming (and I know the danger of doing that) that you are using TSO in
batch since you mention TSOLIB.
Check out the STEPLIB command on www.cbttape.org in file 452. If nothing
else you can look at the source code to see how it does it.
Lionel B. Dyck <><
Website:
I am trying to do the equivalent of TSOLIB for BATCH, i.e., dynamically adding
loadlibs. I do not have spare parent tasks that I can hang a JLB DCB.
It appears that the system is very protective of STEPLIB and will not allow me
to dynamically concat datasets to it (even after closing it in the
I know of one very large customer with many hundred of LPARs, changed they
way they did maintenance.
If they had MVSA, MVSB,MCSC,MVSD, they created a new LPAR MVSE, with all
the maintenance of all products on it. They added it to the sysplex, and
when it proved to work, they removed(killed)
My opinion: If the SYSPLEX capacity for each LPAR is designed to accept the
workload of another LPAR and you have procedures in place to move the load from
one LPAR to another, it should be possible to do that. After all, that is the
main purpose of creating a SYPLEX.
Please let me know if
No. But you can shift the workload and wait for current jobs to finish.
From: IBM Mainframe Discussion List on behalf of
David Spiegel <0468385049d1-dmarc-requ...@listserv.ua.edu>
Sent: Tuesday, July 18, 2023 10:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Hi Tom,
Can you workload shift running Jobs from one LPAR to another?
(Please note too this customer's Initiator setup is different on every
LPAR.)
Regards,
David
On 2023-07-18 09:52, Tom Marchant wrote:
In a Sysplex environment it is possible to shift the workload off of one system
so that
In a Sysplex environment it is possible to shift the workload off of one system
so that it can be IPLed at any time, not just on weekends.
IMO, customers that are stuck in the old way of doing things should not serve
as a model for others.
--
Tom Marchant
On Tue, 18 Jul 2023 06:52:02 -0400,
On Tue, 18 Jul 2023 13:30:18 +, Rob Scott wrote:
>Munif
>
>You could use SDSF REXX to achieve what you want quite easily. You could
>either insert a separator between each DD, or write to a new member of a PDS
>with (maybe) member name = DD name.
>
I did that long ago, target is a UNIX
Munif
You could use SDSF REXX to achieve what you want quite easily. You could either
insert a separator between each DD, or write to a new member of a PDS with
(maybe) member name = DD name.
Sample SDSF REXX statements can be generated using the in-product "RGEN"
command (which will produce
Is there a way (like sdsf XDC) to copy JES2 job output either to a dataset or
ZFS with segregation of
JESMSGLG
JESJCL
JESYSMSG
SMPOUT
SMPRPT
SMPLOG
SYSPRINT etc
rather as a PS.
regards
Munif.
--
For IBM-MAIN
Thanks
We managed to figure out that you need to create a new catalog entry, which is
one of the options in the Actions Menu.
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Kurt J. Quackenbush
Sent: יום ג 18 יולי 2023 15:24
To: IBM-MAIN@LISTSERV.UA.EDU
Mark J wrote:
You can specify most configuration members like LPA, PROG, OMVS as options on
the D IPLINFO command. The response back will display what was used at IPL time.
As Mark wrote, you can specify all "system parameters" (i.e., those in
IEASYSxx) as an operand of DISPLAY IPLINFO to
> There is a column in the dataset list named 'Must be in Master Catalog'. For
> some datasets the value is YES.
> How do I change this to NO or BLANK?
You can't change that value, but you don't need to, because that column is only
tourist information and does not affect z/OSMF's processing.
CEE3204S The system detected a protection exception (System Completion
Code=0C4).
From compile unit TOROLABA:./Objects/object.c at entry point
PyObject_Hash at statement 769 at compile unit offset +1C3A79B4 at
entry offset
+0074 at address 1C3A79B4.
Hi Brian,
One of my customers decided (many years ago) to upgrade software/apply
maintenance once a year (on each of their 4 complexes).
There are not enough weekends in the year to do this more frequently
(due to other groups doing upgrades and "blocked out" weekends).
Regards,
David
On
Hi,
We are in the process of installing z/OS v2.5.
We are using z/OSMF under z/OS v2.3.
We've changed the names of most of the datasets and libraries.
We now have three High Level Qualifiers.
We would like datasets and libraries with an HLQ of SYS1 and CPAC to be
cataloged in a master catalog,
The SDSF command “SYSP” will show them – and if you are z/OS 2.5 you can use
the “L” action against those that have member suffix specifications to show
them in the logical PARMLIB concatenations.
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Mark Jacobs
Sent: 18
All RSU's are not created equal. The quarterly ones (i.e. 2303 2306 2309
2312), are tested by IBM differently and tend to be "easier" to install.
There is NEVER a good reason to skip maintenance for a long period of time.
Only doing maintenance when you install a new copy of the OS is a
29 matches
Mail list logo
