If you need to do this (effectively a move), what you have to do
is allocate the file with a temporary name on the receiving LPAR
(I don't mean &&temp or similar), but a known temp name for this
process. Upon successful move of the data, the sending system
renames the dataset, notifies the receiving system which now
renames the dataset received to the name needed. If that last
step fails, you still have the data on the other side. If the
post to the sending side fails, you still have the data, it
isn't lost.
Doing it this way, if there is a failure, you are not in a
position of having a corrupted file without recovery.
Yes it is a bit tedious, but computers are good at mindless tedium.
Used to do this kind of thing with Connect:Direct. Part of our
regression test system.
HTHs
Steve Thompson
On 2/19/2025 9:41 AM, Mark Jacobs wrote:
Please excuse me for confusing people, I confused myself too. Reading the logs
again, here's the actual scenario.
1) Step one initiates a data transfer to another system in the sysplex.
2) Step two allocates a dataset with the same dataset name for *reasons*.
The dynamic allocation failure that's returned in the log actually occurs on
the remote system. There's a shared enqueue already for the target dataset so
the attempt by the receiving system to allocate the dataset, I assume its
requesting exclusive fails.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&[email protected]
On Wednesday, February 19th, 2025 at 9:01 AM, Paul Gilmartin
<[email protected]> wrote:
On Wed, 19 Feb 2025 12:17:48 +0000, Mark Jacobs [email protected] wrote:
One of the things I'm going to test is whether setting S99NORES in S99FLAG2
might work. If so all we need to do is convince the software vendor to support
setting it on a job-by-job basis.
https://www.ibm.com/docs/en/zos/2.4.0?topic=fields-additional-flags-s99flag2
Note: Data sets being allocated are normally serialized via ENQ with MAJOR name
SYSDSN, MINOR name -data set name-. When S99NORES is set, there is NO data set
serialization and multiple tasks may reference or update the data set
simultaneously, resulting in unpredictable effects. It is the responsibility of
the authorized program setting S99NORES to provide the necessary serialization.
Do you want to do that? It might be a hard sell with the vendor.
"Vendor"? Is that vendor using multiple address spaces?
-- gil
----------------------------------------------------------------------
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
--
Regards,
Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
