Assistance Needed with COBOL File Reading Structure

[Jason Cai]

Subject: Assistance Needed with COBOL File Reading Structure

Dear [Recipient's Name],

I hope this message finds you well.

I am currently working on a COBOL program to read a file with the following 
format: length1, content1, length2, content2, and so on. An example of the data 
in the file is as follows:
```
00F00CFFF00F
0110140003156011
```

I intended to use the following copybook to read the data:
```cobol
05 LL1 PIC 9(2).
05 TT1 OCCURS 1 TO 2 TIMES
   DEPENDING ON LL1.
05 LL2 PIC 9(2).
05 TT2 OCCURS 1 TO 2 TIMES
   DEPENDING ON LL2.
```
However, I encountered an error:
```
IGYGR1137-S "OCCURS DEPENDING ON" object "LL2" was defined in a variably 
located area. Execution results are unpredictable.
```

The suggested structure to avoid this error is as follows:
```cobol
05 LL1 PIC 9(1).
05 LL2 PIC 9(1).
05 TT1 OCCURS 1 TO 2 TIMES
   DEPENDING ON LL1.
   10  TT11PIC X(1).
05 TT2 OCCURS 1 TO 3 TIMES
   DEPENDING ON LL2.
   10  TT21PIC X(1).
```
Unfortunately, this structure does not match the format of the file I need to 
read. Could you please advise on how to correctly read a file with this 
structure using COBOL?

Thank you for your any assistance !

Best regards,

Jason Cai

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer

[Rob Scott]

Ok I will bite.

Please point out what parts of that extract are "grim" and "embarrassing".

Rob Scott
Rocket Software

Get Outlook for Android

From: IBM Mainframe Discussion List  on behalf of 
Lionel B. Dyck <057b0ee5a853-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, June 13, 2024 8:43:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: As a long-time Rexx programmer

EXTERNAL EMAIL




Just be glad we do have a REXX API to invoke SDSF 😊


Lionel B. Dyck <><
Github: https://github.com/lbdyck
System Z Enthusiasts Discord: https://discord.gg/sze

“Worry more about your character than your reputation. Character is what you 
are, reputation merely what others think you are.” - - - John Wooden

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Phil Smith III
Sent: Thursday, June 13, 2024 1:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: As a long-time Rexx programmer

...am I the only one who SMH at the documentation for things like ISFEXEC 
(https://www.ibm.com/docs/en/zos/2.4.0?topic=language-issuing-commands-isfexec)?
 It reads like it was written by someone who doesn't quite understand how 
variables/literals work in Rexx:
--
You issue commands with the ISFEXEC host command as follows:
Address SDSF
"ISFEXEC sdsf-command (options)"
sdsf-command
is a supported SDSF command, including any parameters. If the command contains 
special characters or blanks, enclose it in single quotation marks.
--
The rest of the doc seems to be similar. If only IBM had some Rexx 
experience.oh, wait.

Yes, I'm being snide, but this is just grim. And embarrassing. I realize 
unlikely to be fixed at this late date, of course.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Assistance Needed with COBOL File Reading Structure

[Martin Trübner]

Jason,


try it with this (and use correct numbers- your sample had 0 to 3)


05 LL1 PIC 9(2).
05 TT1 OCCURS 0 TO 3 TIMES
   DEPENDING ON LL1.
05 REMAIN  PIC X(4)

and in working storage section have this:

01 TEMP-WORK.
05 LL2 PIC 9(2).
05 TT2 OCCURS 0 TO 3 TIMES
   DEPENDING ON LL2.


An extra MOVE before you touch TT2.


or multiple repeats of the above



Martin



On 14.06.24 09:39, Jason Cai wrote:

Subject: Assistance Needed with COBOL File Reading Structure

Dear [Recipient's Name],

I hope this message finds you well.

I am currently working on a COBOL program to read a file with the following 
format: length1, content1, length2, content2, and so on. An example of the data 
in the file is as follows:
```
00F00CFFF00F
0110140003156011
```

I intended to use the following copybook to read the data:
```cobol
05 LL1 PIC 9(2).
05 TT1 OCCURS 1 TO 2 TIMES
DEPENDING ON LL1.
05 LL2 PIC 9(2).
05 TT2 OCCURS 1 TO 2 TIMES
DEPENDING ON LL2.
```
However, I encountered an error:
```
IGYGR1137-S "OCCURS DEPENDING ON" object "LL2" was defined in a variably 
located area. Execution results are unpredictable.
```

The suggested structure to avoid this error is as follows:
```cobol
05 LL1 PIC 9(1).
05 LL2 PIC 9(1).
05 TT1 OCCURS 1 TO 2 TIMES
DEPENDING ON LL1.
10  TT11PIC X(1).
05 TT2 OCCURS 1 TO 3 TIMES
DEPENDING ON LL2.
10  TT21PIC X(1).
```
Unfortunately, this structure does not match the format of the file I need to 
read. Could you please advise on how to correctly read a file with this 
structure using COBOL?

Thank you for your any assistance !

Best regards,

Jason Cai

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Assistance Needed with COBOL File Reading Structure

[Bernd Oppolzer]

Hi Martin and Jason,

I agree with Martin that the length / data elements must be processed 
one at a time.

Some additional remarks:

- the length field must have attribute S9(4) comp, because it is a 
binary length field


- I would suggest not to use the OCCURS ... DEPENDING clause at all, but 
unstead work with MOVE with positions,
like this: MOVE SOURCE (X:Y) TO TEMP-WORK ... where X is the position in 
the source string where the length
field of the actual element starts and X is the maximum length plus 2. 
Then you can process the content,
using TEMP-WORK, by examining the length field at the start of 
TEMP-WORK, and then increment X by the

length field plus 2

- is the length of the original source string fixed of variable? Doesn't 
really matter; when looping over this
string, you have to take care to finish processing when the value of X 
reaches the end of the string.


@Martin: we didn't talk for a long time; I'm now working for more than 4 
years with my COBOL/VSE assignment
and consider myself a COBOL expert :-) but still working with PL/1 and 
ASSEMBLER with the other customer.

You know them all ...

HTH, kind regards

Bernd


Am 14.06.2024 um 11:00 schrieb Martin Trübner:

Jason,


try it with this (and use correct numbers- your sample had 0 to 3)


05 LL1 PIC 9(2).
05 TT1 OCCURS 0 TO 3 TIMES
   DEPENDING ON LL1.
05 REMAIN  PIC X(4)

and in working storage section have this:

01 TEMP-WORK.
05 LL2 PIC 9(2).
05 TT2 OCCURS 0 TO 3 TIMES
   DEPENDING ON LL2.


An extra MOVE before you touch TT2.


or multiple repeats of the above



Martin



On 14.06.24 09:39, Jason Cai wrote:

Subject: Assistance Needed with COBOL File Reading Structure

Dear [Recipient's Name],

I hope this message finds you well.

I am currently working on a COBOL program to read a file with the 
following format: length1, content1, length2, content2, and so on. An 
example of the data in the file is as follows:

```
00F00CFFF00F
0110140003156011
```

I intended to use the following copybook to read the data:
```cobol
05 LL1 PIC 9(2).
05 TT1 OCCURS 1 TO 2 TIMES
    DEPENDING ON LL1.
05 LL2 PIC 9(2).
05 TT2 OCCURS 1 TO 2 TIMES
    DEPENDING ON LL2.
```
However, I encountered an error:
```
IGYGR1137-S "OCCURS DEPENDING ON" object "LL2" was defined in a 
variably located area. Execution results are unpredictable.

```

The suggested structure to avoid this error is as follows:
```cobol
05 LL1 PIC 9(1).
05 LL2 PIC 9(1).
05 TT1 OCCURS 1 TO 2 TIMES
    DEPENDING ON LL1.
    10  TT11    PIC X(1).
05 TT2 OCCURS 1 TO 3 TIMES
    DEPENDING ON LL2.
    10  TT21    PIC X(1).
```
Unfortunately, this structure does not match the format of the file I 
need to read. Could you please advise on how to correctly read a file 
with this structure using COBOL?


Thank you for your any assistance !

Best regards,

Jason Cai

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Assistance Needed with COBOL File Reading Structure

[Bernd Oppolzer]

Sorry, Typo ... should read: ... and Y is the maximum length plus 2 ...


Am 14.06.2024 um 13:09 schrieb Bernd Oppolzer:

Hi Martin and Jason,

I agree with Martin that the length / data elements must be processed 
one at a time.

Some additional remarks:

- the length field must have attribute S9(4) comp, because it is a 
binary length field


- I would suggest not to use the OCCURS ... DEPENDING clause at all, 
but unstead work with MOVE with positions,
like this: MOVE SOURCE (X:Y) TO TEMP-WORK ... where X is the position 
in the source string where the length
field of the actual element starts and X is the maximum length plus 2. 
Then you can process the content,
using TEMP-WORK, by examining the length field at the start of 
TEMP-WORK, and then increment X by the

length field plus 2

- is the length of the original source string fixed of variable? 
Doesn't really matter; when looping over this
string, you have to take care to finish processing when the value of X 
reaches the end of the string.


@Martin: we didn't talk for a long time; I'm now working for more than 
4 years with my COBOL/VSE assignment
and consider myself a COBOL expert :-) but still working with PL/1 and 
ASSEMBLER with the other customer.

You know them all ...

HTH, kind regards

Bernd


Am 14.06.2024 um 11:00 schrieb Martin Trübner:

Jason,


try it with this (and use correct numbers- your sample had 0 to 3)


05 LL1 PIC 9(2).
05 TT1 OCCURS 0 TO 3 TIMES
   DEPENDING ON LL1.
05 REMAIN  PIC X(4)

and in working storage section have this:

01 TEMP-WORK.
05 LL2 PIC 9(2).
05 TT2 OCCURS 0 TO 3 TIMES
   DEPENDING ON LL2.


An extra MOVE before you touch TT2.


or multiple repeats of the above



Martin



On 14.06.24 09:39, Jason Cai wrote:

Subject: Assistance Needed with COBOL File Reading Structure

Dear [Recipient's Name],

I hope this message finds you well.

I am currently working on a COBOL program to read a file with the 
following format: length1, content1, length2, content2, and so on. 
An example of the data in the file is as follows:

```
00F00CFFF00F
0110140003156011
```

I intended to use the following copybook to read the data:
```cobol
05 LL1 PIC 9(2).
05 TT1 OCCURS 1 TO 2 TIMES
    DEPENDING ON LL1.
05 LL2 PIC 9(2).
05 TT2 OCCURS 1 TO 2 TIMES
    DEPENDING ON LL2.
```
However, I encountered an error:
```
IGYGR1137-S "OCCURS DEPENDING ON" object "LL2" was defined in a 
variably located area. Execution results are unpredictable.

```

The suggested structure to avoid this error is as follows:
```cobol
05 LL1 PIC 9(1).
05 LL2 PIC 9(1).
05 TT1 OCCURS 1 TO 2 TIMES
    DEPENDING ON LL1.
    10  TT11    PIC X(1).
05 TT2 OCCURS 1 TO 3 TIMES
    DEPENDING ON LL2.
    10  TT21    PIC X(1).
```
Unfortunately, this structure does not match the format of the file 
I need to read. Could you please advise on how to correctly read a 
file with this structure using COBOL?


Thank you for your any assistance !

Best regards,

Jason Cai

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Assistance Needed with COBOL File Reading Structure

[Jason Cai]

Martin 

Thank you for your response. I have carefully reviewed the file and have a few 
questions regarding handling hexadecimal numbers for the length part and how it 
integrates with the OCCURS DEPENDING ON clause.


Questions:

The file that needs to be processed contains lengths in hexadecimal format. The 
length fields can be of various byte sizes: 2, 4, or 6 bytes, etc. Can we use 
PIC 9(2), PIC 9(4), or PIC 9(2) COMP to directly read these hexadecimal numbers 
and use them for the OCCURS DEPENDING ON clause?

Regarding the file section:

cobol
Copy code
FILE SECTION.
FD  INPUT-FILE.
01  INPUT-RECORD.
How should this be written if we need to handle multiple lengths and their 
corresponding content using the OCCURS clause?

Thank you for your assistance!

Jason 


On Fri, 14 Jun 2024 11:00:17 +0200, Martin Trübner  wrote:

>Jason,
>
>
>try it with this (and use correct numbers- your sample had 0 to 3)
>
>
>05 LL1 PIC 9(2).
>05 TT1 OCCURS 0 TO 3 TIMES
>DEPENDING ON LL1.
>05 REMAIN  PIC X(4)
>
>and in working storage section have this:
>
>01 TEMP-WORK.
>05 LL2 PIC 9(2).
>05 TT2 OCCURS 0 TO 3 TIMES
>DEPENDING ON LL2.
>
>
>An extra MOVE before you touch TT2.
>
>
>or multiple repeats of the above
>
>
>
>Martin
>
>
>
>On 14.06.24 09:39, Jason Cai wrote:
>> Subject: Assistance Needed with COBOL File Reading Structure
>>
>> Dear [Recipient's Name],
>>
>> I hope this message finds you well.
>>
>> I am currently working on a COBOL program to read a file with the following 
>> format: length1, content1, length2, content2, and so on. An example of the 
>> data in the file is as follows:
>> ```
>> 00F00CFFF00F
>> 0110140003156011
>> ```
>>
>> I intended to use the following copybook to read the data:
>> ```cobol
>> 05 LL1 PIC 9(2).
>> 05 TT1 OCCURS 1 TO 2 TIMES
>> DEPENDING ON LL1.
>> 05 LL2 PIC 9(2).
>> 05 TT2 OCCURS 1 TO 2 TIMES
>> DEPENDING ON LL2.
>> ```
>> However, I encountered an error:
>> ```
>> IGYGR1137-S "OCCURS DEPENDING ON" object "LL2" was defined in a variably 
>> located area. Execution results are unpredictable.
>> ```
>>
>> The suggested structure to avoid this error is as follows:
>> ```cobol
>> 05 LL1 PIC 9(1).
>> 05 LL2 PIC 9(1).
>> 05 TT1 OCCURS 1 TO 2 TIMES
>> DEPENDING ON LL1.
>> 10  TT11PIC X(1).
>> 05 TT2 OCCURS 1 TO 3 TIMES
>> DEPENDING ON LL2.
>> 10  TT21PIC X(1).
>> ```
>> Unfortunately, this structure does not match the format of the file I need 
>> to read. Could you please advise on how to correctly read a file with this 
>> structure using COBOL?
>>
>> Thank you for your any assistance !
>>
>> Best regards,
>>
>> Jason Cai
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Assistance Needed with COBOL File Reading Structure

[Jason Cai]

Bernd

Thank you for providing another approach to read and process the file. I have a 
few questions to confirm my understanding:
Q1:
File Section Definition:

cobol
Copy code
FILE SECTION.
FD  INPUT-FILE.
01  INPUT-RECORD  PIC X(80).
Is it correct ?

Q2:
Do hexadecimal lengths require special handling?
Q3:
How do we identify which parts of the 80-column data represent the length and 
which parts represent the content, given that the length is a hexadecimal 
number?

Thank you for your assistance!

Best regards,

Jason Cai

On Fri, 14 Jun 2024 13:13:08 +0200, Bernd Oppolzer  
wrote:

>Sorry, Typo ... should read: ... and Y is the maximum length plus 2 ...
>
>
>Am 14.06.2024 um 13:09 schrieb Bernd Oppolzer:
>> Hi Martin and Jason,
>>
>> I agree with Martin that the length / data elements must be processed
>> one at a time.
>> Some additional remarks:
>>
>> - the length field must have attribute S9(4) comp, because it is a
>> binary length field
>>
>> - I would suggest not to use the OCCURS ... DEPENDING clause at all,
>> but unstead work with MOVE with positions,
>> like this: MOVE SOURCE (X:Y) TO TEMP-WORK ... where X is the position
>> in the source string where the length
>> field of the actual element starts and X is the maximum length plus 2.
>> Then you can process the content,
>> using TEMP-WORK, by examining the length field at the start of
>> TEMP-WORK, and then increment X by the
>> length field plus 2
>>
>> - is the length of the original source string fixed of variable?
>> Doesn't really matter; when looping over this
>> string, you have to take care to finish processing when the value of X
>> reaches the end of the string.
>>
>> @Martin: we didn't talk for a long time; I'm now working for more than
>> 4 years with my COBOL/VSE assignment
>> and consider myself a COBOL expert :-) but still working with PL/1 and
>> ASSEMBLER with the other customer.
>> You know them all ...
>>
>> HTH, kind regards
>>
>> Bernd
>>
>>
>> Am 14.06.2024 um 11:00 schrieb Martin Trübner:
>>> Jason,
>>>
>>>
>>> try it with this (and use correct numbers- your sample had 0 to 3)
>>>
>>>
>>> 05 LL1 PIC 9(2).
>>> 05 TT1 OCCURS 0 TO 3 TIMES
>>>    DEPENDING ON LL1.
>>> 05 REMAIN  PIC X(4)
>>>
>>> and in working storage section have this:
>>>
>>> 01 TEMP-WORK.
>>> 05 LL2 PIC 9(2).
>>> 05 TT2 OCCURS 0 TO 3 TIMES
>>>    DEPENDING ON LL2.
>>>
>>>
>>> An extra MOVE before you touch TT2.
>>>
>>>
>>> or multiple repeats of the above
>>>
>>>
>>>
>>> Martin
>>>
>>>
>>>
>>> On 14.06.24 09:39, Jason Cai wrote:
 Subject: Assistance Needed with COBOL File Reading Structure

 Dear [Recipient's Name],

 I hope this message finds you well.

 I am currently working on a COBOL program to read a file with the
 following format: length1, content1, length2, content2, and so on.
 An example of the data in the file is as follows:
 ```
 00F00CFFF00F
 0110140003156011
 ```

 I intended to use the following copybook to read the data:
 ```cobol
 05 LL1 PIC 9(2).
 05 TT1 OCCURS 1 TO 2 TIMES
     DEPENDING ON LL1.
 05 LL2 PIC 9(2).
 05 TT2 OCCURS 1 TO 2 TIMES
     DEPENDING ON LL2.
 ```
 However, I encountered an error:
 ```
 IGYGR1137-S "OCCURS DEPENDING ON" object "LL2" was defined in a
 variably located area. Execution results are unpredictable.
 ```

 The suggested structure to avoid this error is as follows:
 ```cobol
 05 LL1 PIC 9(1).
 05 LL2 PIC 9(1).
 05 TT1 OCCURS 1 TO 2 TIMES
     DEPENDING ON LL1.
     10  TT11    PIC X(1).
 05 TT2 OCCURS 1 TO 3 TIMES
     DEPENDING ON LL2.
     10  TT21    PIC X(1).
 ```
 Unfortunately, this structure does not match the format of the file
 I need to read. Could you please advise on how to correctly read a
 file with this structure using COBOL?

 Thank you for your any assistance !

 Best regards,

 Jason Cai

 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN
>>>
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscri

Re: Assistance Needed with COBOL File Reading Structure

[Martin Trübner]

Jason,


as Bern pointed out you need to define the field as COMP (or new BINARY) 
- there are 2, 4 or 8 byte binary fields- no 6 bytes- but you can 
redefine a 8 byte binary field with a two byte filler and 6 bytes for 
the binary number.



Martin

On 14.06.24 14:14, Jason Cai wrote:

Bernd

Thank you for providing another approach to read and process the file. I have a 
few questions to confirm my understanding:
Q1:
File Section Definition:

cobol
Copy code
FILE SECTION.
FD  INPUT-FILE.
01  INPUT-RECORD  PIC X(80).
Is it correct ?

Q2:
Do hexadecimal lengths require special handling?
Q3:
How do we identify which parts of the 80-column data represent the length and 
which parts represent the content, given that the length is a hexadecimal 
number?

Thank you for your assistance!

Best regards,

Jason Cai

On Fri, 14 Jun 2024 13:13:08 +0200, Bernd Oppolzer  
wrote:


Sorry, Typo ... should read: ... and Y is the maximum length plus 2 ...


Am 14.06.2024 um 13:09 schrieb Bernd Oppolzer:

Hi Martin and Jason,

I agree with Martin that the length / data elements must be processed
one at a time.
Some additional remarks:

- the length field must have attribute S9(4) comp, because it is a
binary length field

- I would suggest not to use the OCCURS ... DEPENDING clause at all,
but unstead work with MOVE with positions,
like this: MOVE SOURCE (X:Y) TO TEMP-WORK ... where X is the position
in the source string where the length
field of the actual element starts and X is the maximum length plus 2.
Then you can process the content,
using TEMP-WORK, by examining the length field at the start of
TEMP-WORK, and then increment X by the
length field plus 2

- is the length of the original source string fixed of variable?
Doesn't really matter; when looping over this
string, you have to take care to finish processing when the value of X
reaches the end of the string.

@Martin: we didn't talk for a long time; I'm now working for more than
4 years with my COBOL/VSE assignment
and consider myself a COBOL expert :-) but still working with PL/1 and
ASSEMBLER with the other customer.
You know them all ...

HTH, kind regards

Bernd


Am 14.06.2024 um 11:00 schrieb Martin Trübner:

Jason,


try it with this (and use correct numbers- your sample had 0 to 3)


05 LL1 PIC 9(2).
05 TT1 OCCURS 0 TO 3 TIMES
    DEPENDING ON LL1.
05 REMAIN  PIC X(4)

and in working storage section have this:

01 TEMP-WORK.
05 LL2 PIC 9(2).
05 TT2 OCCURS 0 TO 3 TIMES
    DEPENDING ON LL2.


An extra MOVE before you touch TT2.


or multiple repeats of the above



Martin



On 14.06.24 09:39, Jason Cai wrote:

Subject: Assistance Needed with COBOL File Reading Structure

Dear [Recipient's Name],

I hope this message finds you well.

I am currently working on a COBOL program to read a file with the
following format: length1, content1, length2, content2, and so on.
An example of the data in the file is as follows:
```
00F00CFFF00F
0110140003156011
```

I intended to use the following copybook to read the data:
```cobol
05 LL1 PIC 9(2).
05 TT1 OCCURS 1 TO 2 TIMES
     DEPENDING ON LL1.
05 LL2 PIC 9(2).
05 TT2 OCCURS 1 TO 2 TIMES
     DEPENDING ON LL2.
```
However, I encountered an error:
```
IGYGR1137-S "OCCURS DEPENDING ON" object "LL2" was defined in a
variably located area. Execution results are unpredictable.
```

The suggested structure to avoid this error is as follows:
```cobol
05 LL1 PIC 9(1).
05 LL2 PIC 9(1).
05 TT1 OCCURS 1 TO 2 TIMES
     DEPENDING ON LL1.
     10  TT11    PIC X(1).
05 TT2 OCCURS 1 TO 3 TIMES
     DEPENDING ON LL2.
     10  TT21    PIC X(1).
```
Unfortunately, this structure does not match the format of the file
I need to read. Could you please advise on how to correctly read a
file with this structure using COBOL?

Thank you for your any assistance !

Best regards,

Jason Cai

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send emailtolists...@listserv.ua.edu   with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu  with the message: INFO IBM-MAIN

Re: WS JES2 SPOOL OFFLOAD

[Allan Staller]

Classification: Confidential

Check the selection criteria in the $TOFFLOAD command, It should do what you 
want,


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Samuel Alejandro Díaz Chávez
Sent: Thursday, June 13, 2024 9:46 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: WS JES2 SPOOL OFFLOAD

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Good evening and best regards to all.

I would like to ask about an issue which is new for those of us who are 
implementing the SPOOL OFFLOAD option.

But we want to generate the SYSOUT transmit to the OFFLOAD file, but we want 
the selection or the option to be for the time that the output has in the spool.

Example: If we have processes that start with APSP*, and they have more than 7 
days in the spool, that the transmit is done.

Thank you very much for your support.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

DB2 V12 RSU2403

[Steve Beaver]

Upfront - I am not a DB2 SYSPROG, SYSADM, or Programmer

 

I have pulled in and applied DB2 V12 RSU2403.  That was the easy part.

 

There are 134 PTF's with HOLD ACTION and that is where  trouble is going to

Begin.

 

Does anyone have a Home Grown implementation document to help me get

Through these 134 PTF's with HOLD.

 

Thanks

 

Stev 

 

 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Seymour J Metz]

If you are running authorized you can MODESET to key zero and modify the DEB.

Measure twice cut once.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of 
Tony Thigpen 
Sent: Friday, June 14, 2024 11:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Getting dasd info

All,

I have a z/VSE program that I want to start using with z/OS. The program
issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that
are either volume specific or subsystem specific. Not file specific.

My first question is in the area of getting access to a specific volume
on z/OS.

In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.

On z/OS, I expect I need to perform an OPEN against the volume using
something like:
//SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD

Any pointers would be appreciated.

My second question relates to 'authority'.

On z/VSE, I have to tell the operating system that I am actually 'DSF'
before it will allow me to issue these CCWs.

Do I have to do something special on z/OS?


Thanks,

Tony Thigpen

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Getting dasd info

[Tony Thigpen]

All,

I have a z/VSE program that I want to start using with z/OS. The program 
issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that 
are either volume specific or subsystem specific. Not file specific.


My first question is in the area of getting access to a specific volume 
on z/OS.


In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.

On z/OS, I expect I need to perform an OPEN against the volume using 
something like:

//SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD

Any pointers would be appreciated.

My second question relates to 'authority'.

On z/VSE, I have to tell the operating system that I am actually 'DSF' 
before it will allow me to issue these CCWs.


Do I have to do something special on z/OS?


Thanks,

Tony Thigpen

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer

[Phil Smith III]

"If the command contains special characters or blanks, enclose it in single 
quotation marks."

Might not be the best example, but it's clear from the doc that whoever wrote 
it doesn't understand that unassigned Rexx variables return their literal 
values.

Point is, if this is an SDSF special thing, then that isn't clear. If it's 
referring to "Hey, if you want to pass something like
xyz;abc
then you need to either have that in a variable and specify the variable OR put 
it in quotes because that's how Rexx works", then that's different. (And is 
what is pretty clear from some other places in the doc, though perhaps not this 
specific case.)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Rob 
Scott
Sent: Friday, June 14, 2024 4:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: As a long-time Rexx programmer

Ok I will bite.

Please point out what parts of that extract are "grim" and "embarrassing".

Rob Scott
Rocket Software

Get Outlook for Android 
From: IBM Mainframe Discussion List  on behalf of 
Lionel B. Dyck <057b0ee5a853-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, June 13, 2024 8:43:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: As a long-time Rexx programmer

EXTERNAL EMAIL




Just be glad we do have a REXX API to invoke SDSF 😊


Lionel B. Dyck <><
Github: https://github.com/lbdyck
System Z Enthusiasts Discord: https://discord.gg/sze

“Worry more about your character than your reputation. Character is what you 
are, reputation merely what others think you are.” - - - John Wooden

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Phil Smith III
Sent: Thursday, June 13, 2024 1:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: As a long-time Rexx programmer

...am I the only one who SMH at the documentation for things like ISFEXEC 
(https://www.ibm.com/docs/en/zos/2.4.0?topic=language-issuing-commands-isfexec)?
 It reads like it was written by someone who doesn't quite understand how 
variables/literals work in Rexx:
--
You issue commands with the ISFEXEC host command as follows:
Address SDSF
"ISFEXEC sdsf-command (options)"
sdsf-command
is a supported SDSF command, including any parameters. If the command contains 
special characters or blanks, enclose it in single quotation marks.
--
The rest of the doc seems to be similar. If only IBM had some Rexx 
experience.oh, wait.

Yes, I'm being snide, but this is just grim. And embarrassing. I realize 
unlikely to be fixed at this late date, of course.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer

[Seymour J Metz]

My experience has been that product documntation often summarizes, incorrectly, 
rules for, e.g., CLIST, JCL, REXX, instead of referring the reader to the 
appropriate documentation.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of 
Phil Smith III 
Sent: Friday, June 14, 2024 11:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: As a long-time Rexx programmer

"If the command contains special characters or blanks, enclose it in single 
quotation marks."

Might not be the best example, but it's clear from the doc that whoever wrote 
it doesn't understand that unassigned Rexx variables return their literal 
values.

Point is, if this is an SDSF special thing, then that isn't clear. If it's 
referring to "Hey, if you want to pass something like
xyz;abc
then you need to either have that in a variable and specify the variable OR put 
it in quotes because that's how Rexx works", then that's different. (And is 
what is pretty clear from some other places in the doc, though perhaps not this 
specific case.)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Rob 
Scott
Sent: Friday, June 14, 2024 4:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: As a long-time Rexx programmer

Ok I will bite.

Please point out what parts of that extract are "grim" and "embarrassing".

Rob Scott
Rocket Software

Get Outlook for Android 
From: IBM Mainframe Discussion List  on behalf of 
Lionel B. Dyck <057b0ee5a853-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, June 13, 2024 8:43:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: As a long-time Rexx programmer

EXTERNAL EMAIL




Just be glad we do have a REXX API to invoke SDSF 😊


Lionel B. Dyck <><
Github: https://github.com/lbdyck
System Z Enthusiasts Discord: https://discord.gg/sze

“Worry more about your character than your reputation. Character is what you 
are, reputation merely what others think you are.” - - - John Wooden

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Phil Smith III
Sent: Thursday, June 13, 2024 1:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: As a long-time Rexx programmer

...am I the only one who SMH at the documentation for things like ISFEXEC 
(https://www.ibm.com/docs/en/zos/2.4.0?topic=language-issuing-commands-isfexec)?
 It reads like it was written by someone who doesn't quite understand how 
variables/literals work in Rexx:
--
You issue commands with the ISFEXEC host command as follows:
Address SDSF
"ISFEXEC sdsf-command (options)"
sdsf-command
is a supported SDSF command, including any parameters. If the command contains 
special characters or blanks, enclose it in single quotation marks.
--
The rest of the doc seems to be similar. If only IBM had some Rexx 
experience.oh, wait.

Yes, I'm being snide, but this is just grim. And embarrassing. I realize 
unlikely to be fixed at this late date, of course.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@

Re: Getting dasd info

[Mike Shaw]

Tony,

You can run in problem program state and key and issue a UCBSCAN macro to
get a list of UCBs and UCB copies for that z/OS system. You can then run
that returned list and choose only the online DASD UCBs. For each of those
that you are interested in, issue an LSPACE SVC specifying the UCB address.
That will get you a good picture of free space info for that volume, and
it's quick.

To go deeper and get a list of all data sets on the volume and/or a volume
map, you have to read the VTOC and process it. You can do that without
being APF authorized also, if the volume is allocated to your job step.

The CVAFTST macro will tell you whether or not a particular DASD volume has
an indexed VTOC or not.

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.


On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:

> All,
>
> I have a z/VSE program that I want to start using with z/OS. The program
> issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that
> are either volume specific or subsystem specific. Not file specific.
>
> My first question is in the area of getting access to a specific volume
> on z/OS.
>
> In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.
>
> On z/OS, I expect I need to perform an OPEN against the volume using
> something like:
> //SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD
>
> Any pointers would be appreciated.
>
> My second question relates to 'authority'.
>
> On z/VSE, I have to tell the operating system that I am actually 'DSF'
> before it will allow me to issue these CCWs.
>
> Do I have to do something special on z/OS?
>
>
> Thanks,
>
> Tony Thigpen
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Matthew Stitt]

Take a look at file 527 on the CBT tape.  Program(s) DADSM and LISTICAT.  Both 
programs do a scan of the disk volumes and generate reports on VTOC, VVDS, etc.

Matthew

On Fri, 14 Jun 2024 12:08:54 -0400, Mike Shaw  wrote:

>Tony,
>
>You can run in problem program state and key and issue a UCBSCAN macro to
>get a list of UCBs and UCB copies for that z/OS system. You can then run
>that returned list and choose only the online DASD UCBs. For each of those
>that you are interested in, issue an LSPACE SVC specifying the UCB address.
>That will get you a good picture of free space info for that volume, and
>it's quick.
>
>To go deeper and get a list of all data sets on the volume and/or a volume
>map, you have to read the VTOC and process it. You can do that without
>being APF authorized also, if the volume is allocated to your job step.
>
>The CVAFTST macro will tell you whether or not a particular DASD volume has
>an indexed VTOC or not.
>
>Mike Shaw
>MVS/QuickRef Support Group
>Chicago-Soft, Ltd.
>
>
>On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:
>
>> All,
>>
>> I have a z/VSE program that I want to start using with z/OS. The program
>> issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that
>> are either volume specific or subsystem specific. Not file specific.
>>
>> My first question is in the area of getting access to a specific volume
>> on z/OS.
>>
>> In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.
>>
>> On z/OS, I expect I need to perform an OPEN against the volume using
>> something like:
>> //SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD
>>
>> Any pointers would be appreciated.
>>
>> My second question relates to 'authority'.
>>
>> On z/VSE, I have to tell the operating system that I am actually 'DSF'
>> before it will allow me to issue these CCWs.
>>
>> Do I have to do something special on z/OS?
>>
>>
>> Thanks,
>>
>> Tony Thigpen
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Farley, Peter]

Doesn’t physical scan of VTOC/VVDS areas on DASD (or for that matter directly 
issuing CCW’s to any DASD for any reason) also require at least SAF 
authorization (if not also APF authorization) to allow access under z/OS?

Peter

From: IBM Mainframe Discussion List  On Behalf Of 
Matthew Stitt
Sent: Friday, June 14, 2024 1:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting dasd info


Take a look at file 527 on the CBT tape.  Program(s) DADSM and LISTICAT.  Both 
programs do a scan of the disk volumes and generate reports on VTOC, VVDS, etc.



Matthew



On Fri, 14 Jun 2024 12:08:54 -0400, Mike Shaw  wrote:



>Tony,

>

>You can run in problem program state and key and issue a UCBSCAN macro to

>get a list of UCBs and UCB copies for that z/OS system. You can then run

>that returned list and choose only the online DASD UCBs. For each of those

>that you are interested in, issue an LSPACE SVC specifying the UCB address.

>That will get you a good picture of free space info for that volume, and

>it's quick.

>

>To go deeper and get a list of all data sets on the volume and/or a volume

>map, you have to read the VTOC and process it. You can do that without

>being APF authorized also, if the volume is allocated to your job step.

>

>The CVAFTST macro will tell you whether or not a particular DASD volume has

>an indexed VTOC or not.

>

>Mike Shaw

>MVS/QuickRef Support Group

>Chicago-Soft, Ltd.

>

>

>On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:

>

>> All,

>>

>> I have a z/VSE program that I want to start using with z/OS. The program

>> issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that

>> are either volume specific or subsystem specific. Not file specific.

>>

>> My first question is in the area of getting access to a specific volume

>> on z/OS.

>>

>> In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.

>>

>> On z/OS, I expect I need to perform an OPEN against the volume using

>> something like:

>> //SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD

>>

>> Any pointers would be appreciated.

>>

>> My second question relates to 'authority'.

>>

>> On z/VSE, I have to tell the operating system that I am actually 'DSF'

>> before it will allow me to issue these CCWs.

>>

>> Do I have to do something special on z/OS?

>>

>>

>> Thanks,

>>

>> Tony Thigpen

--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Seymour J Metz]

Either SAF or APF, depending on what you are doing,, except for those cases 
where there is an unprivileged interface for specific types of access.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of 
Farley, Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
Sent: Friday, June 14, 2024 1:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting dasd info

Doesn’t physical scan of VTOC/VVDS areas on DASD (or for that matter directly 
issuing CCW’s to any DASD for any reason) also require at least SAF 
authorization (if not also APF authorization) to allow access under z/OS?

Peter

From: IBM Mainframe Discussion List  On Behalf Of 
Matthew Stitt
Sent: Friday, June 14, 2024 1:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting dasd info


Take a look at file 527 on the CBT tape.  Program(s) DADSM and LISTICAT.  Both 
programs do a scan of the disk volumes and generate reports on VTOC, VVDS, etc.



Matthew



On Fri, 14 Jun 2024 12:08:54 -0400, Mike Shaw  wrote:



>Tony,

>

>You can run in problem program state and key and issue a UCBSCAN macro to

>get a list of UCBs and UCB copies for that z/OS system. You can then run

>that returned list and choose only the online DASD UCBs. For each of those

>that you are interested in, issue an LSPACE SVC specifying the UCB address.

>That will get you a good picture of free space info for that volume, and

>it's quick.

>

>To go deeper and get a list of all data sets on the volume and/or a volume

>map, you have to read the VTOC and process it. You can do that without

>being APF authorized also, if the volume is allocated to your job step.

>

>The CVAFTST macro will tell you whether or not a particular DASD volume has

>an indexed VTOC or not.

>

>Mike Shaw

>MVS/QuickRef Support Group

>Chicago-Soft, Ltd.

>

>

>On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:

>

>> All,

>>

>> I have a z/VSE program that I want to start using with z/OS. The program

>> issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that

>> are either volume specific or subsystem specific. Not file specific.

>>

>> My first question is in the area of getting access to a specific volume

>> on z/OS.

>>

>> In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.

>>

>> On z/OS, I expect I need to perform an OPEN against the volume using

>> something like:

>> //SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD

>>

>> Any pointers would be appreciated.

>>

>> My second question relates to 'authority'.

>>

>> On z/VSE, I have to tell the operating system that I am actually 'DSF'

>> before it will allow me to issue these CCWs.

>>

>> Do I have to do something special on z/OS?

>>

>>

>> Thanks,

>>

>> Tony Thigpen

--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Mike Shaw]

No. With the right combination of DYNALLOC, OPEN and RDJFCB you can open
the VTOC and execute a channel program that reads the entire VTOC without
any kind of SAF authorization. It can also be read with BSAM but that is a
little slower.

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd

On Fri, Jun 14, 2024, 1:17 PM Farley, Peter <
031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:

> Doesn’t physical scan of VTOC/VVDS areas on DASD (or for that matter
> directly issuing CCW’s to any DASD for any reason) also require at least
> SAF authorization (if not also APF authorization) to allow access under
> z/OS?
>
> Peter
>
> From: IBM Mainframe Discussion List  On Behalf
> Of Matthew Stitt
> Sent: Friday, June 14, 2024 1:00 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Getting dasd info
>
>
> Take a look at file 527 on the CBT tape.  Program(s) DADSM and LISTICAT.
> Both programs do a scan of the disk volumes and generate reports on VTOC,
> VVDS, etc.
>
>
>
> Matthew
>
>
>
> On Fri, 14 Jun 2024 12:08:54 -0400, Mike Shaw 
> wrote:
>
>
>
> >Tony,
>
> >
>
> >You can run in problem program state and key and issue a UCBSCAN macro to
>
> >get a list of UCBs and UCB copies for that z/OS system. You can then run
>
> >that returned list and choose only the online DASD UCBs. For each of those
>
> >that you are interested in, issue an LSPACE SVC specifying the UCB
> address.
>
> >That will get you a good picture of free space info for that volume, and
>
> >it's quick.
>
> >
>
> >To go deeper and get a list of all data sets on the volume and/or a volume
>
> >map, you have to read the VTOC and process it. You can do that without
>
> >being APF authorized also, if the volume is allocated to your job step.
>
> >
>
> >The CVAFTST macro will tell you whether or not a particular DASD volume
> has
>
> >an indexed VTOC or not.
>
> >
>
> >Mike Shaw
>
> >MVS/QuickRef Support Group
>
> >Chicago-Soft, Ltd.
>
> >
>
> >
>
> >On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:
>
> >
>
> >> All,
>
> >>
>
> >> I have a z/VSE program that I want to start using with z/OS. The program
>
> >> issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that
>
> >> are either volume specific or subsystem specific. Not file specific.
>
> >>
>
> >> My first question is in the area of getting access to a specific volume
>
> >> on z/OS.
>
> >>
>
> >> In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.
>
> >>
>
> >> On z/OS, I expect I need to perform an OPEN against the volume using
>
> >> something like:
>
> >> //SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD
>
> >>
>
> >> Any pointers would be appreciated.
>
> >>
>
> >> My second question relates to 'authority'.
>
> >>
>
> >> On z/VSE, I have to tell the operating system that I am actually 'DSF'
>
> >> before it will allow me to issue these CCWs.
>
> >>
>
> >> Do I have to do something special on z/OS?
>
> >>
>
> >>
>
> >> Thanks,
>
> >>
>
> >> Tony Thigpen
>
> --
>
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and confidential.
> If the reader of the message is not the intended recipient or an authorized
> representative of the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please notify us immediately by
> e-mail and delete the message and any attachments from your system.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer

[Rob Scott]

I must admit that I find nothing amiss with the quoted section.

 It describes the syntax requirements of the SDSF-specific ISFEXEC verb.

It does not get into any generic REXX techniques to provide the statement 
buffer to the verb as that is not required in this case.

 Contrast that with the documentation for ISFSLASH that does include required 
REXX techniques as it supports alternate input using stem variables.

The product documentation is written by information development team members, 
but based on input provided by the development team. In this case, that 
developer (not me) has decades of asm, plx and rexx experience and is fully 
aware of the nuances of the language.

The documentation will always be updated when required for the current (most 
recent) release.



Rob Scott
Rocket Software

Get Outlook for Android

From: IBM Mainframe Discussion List  on behalf of 
Phil Smith III 
Sent: Friday, June 14, 2024 5:51:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: As a long-time Rexx programmer

EXTERNAL EMAIL




"If the command contains special characters or blanks, enclose it in single 
quotation marks."

Might not be the best example, but it's clear from the doc that whoever wrote 
it doesn't understand that unassigned Rexx variables return their literal 
values.

Point is, if this is an SDSF special thing, then that isn't clear. If it's 
referring to "Hey, if you want to pass something like
xyz;abc
then you need to either have that in a variable and specify the variable OR put 
it in quotes because that's how Rexx works", then that's different. (And is 
what is pretty clear from some other places in the doc, though perhaps not this 
specific case.)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Rob 
Scott
Sent: Friday, June 14, 2024 4:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: As a long-time Rexx programmer

Ok I will bite.

Please point out what parts of that extract are "grim" and "embarrassing".

Rob Scott
Rocket Software

Get Outlook for Android> 

From: IBM Mainframe Discussion List  on behalf of 
Lionel B. Dyck <057b0ee5a853-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, June 13, 2024 8:43:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: As a long-time Rexx programmer

EXTERNAL EMAIL




Just be glad we do have a REXX API to invoke SDSF 😊


Lionel B. Dyck <><
Github: 
https://github.com/lbdyck>
System Z Enthusiasts Discord: 
https://discord.gg/sze>

“Worry more about your character than your reputation. Character is what you 
are, reputation merely what others think you are.” - - - John Wooden

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Phil Smith III
Sent: Thursday, June 13, 2024 1:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: As a long-time Rexx programmer

...am I the only one who SMH at the documentation for things like ISFEXEC 
(https://www.ibm.com/docs/en/zos/2.4.0?topic=language-issuing-commands-isfexec>)?
 It reads like it was written by someone who doesn't quite understand how 
variables/literals work in Rexx:
--
You issue commands with the ISFEXEC host command as follows:
Address SDSF
"ISFEXEC sdsf-command (options)"
sdsf-command
is a supported SDSF command, including any parameters. If the command contains 
special characters or blanks, enclose it in single quotation marks.
--
The rest of the doc seems to be similar. If only IBM had some Rexx 
experience.oh, wait.

Yes, I'm being snide, but this is just grim. And embarrassing. I realize 
unlikely to be fixed at this late date, of course.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences

Re: Getting dasd info

[Seymour J Metz]

The OP was asking about scanning the entire volume, not just the VTOC.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of 
Mike Shaw 
Sent: Friday, June 14, 2024 1:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting dasd info

No. With the right combination of DYNALLOC, OPEN and RDJFCB you can open
the VTOC and execute a channel program that reads the entire VTOC without
any kind of SAF authorization. It can also be read with BSAM but that is a
little slower.

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd

On Fri, Jun 14, 2024, 1:17 PM Farley, Peter <
031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:

> Doesn’t physical scan of VTOC/VVDS areas on DASD (or for that matter
> directly issuing CCW’s to any DASD for any reason) also require at least
> SAF authorization (if not also APF authorization) to allow access under
> z/OS?
>
> Peter
>
> From: IBM Mainframe Discussion List  On Behalf
> Of Matthew Stitt
> Sent: Friday, June 14, 2024 1:00 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Getting dasd info
>
>
> Take a look at file 527 on the CBT tape.  Program(s) DADSM and LISTICAT.
> Both programs do a scan of the disk volumes and generate reports on VTOC,
> VVDS, etc.
>
>
>
> Matthew
>
>
>
> On Fri, 14 Jun 2024 12:08:54 -0400, Mike Shaw 
> wrote:
>
>
>
> >Tony,
>
> >
>
> >You can run in problem program state and key and issue a UCBSCAN macro to
>
> >get a list of UCBs and UCB copies for that z/OS system. You can then run
>
> >that returned list and choose only the online DASD UCBs. For each of those
>
> >that you are interested in, issue an LSPACE SVC specifying the UCB
> address.
>
> >That will get you a good picture of free space info for that volume, and
>
> >it's quick.
>
> >
>
> >To go deeper and get a list of all data sets on the volume and/or a volume
>
> >map, you have to read the VTOC and process it. You can do that without
>
> >being APF authorized also, if the volume is allocated to your job step.
>
> >
>
> >The CVAFTST macro will tell you whether or not a particular DASD volume
> has
>
> >an indexed VTOC or not.
>
> >
>
> >Mike Shaw
>
> >MVS/QuickRef Support Group
>
> >Chicago-Soft, Ltd.
>
> >
>
> >
>
> >On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:
>
> >
>
> >> All,
>
> >>
>
> >> I have a z/VSE program that I want to start using with z/OS. The program
>
> >> issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that
>
> >> are either volume specific or subsystem specific. Not file specific.
>
> >>
>
> >> My first question is in the area of getting access to a specific volume
>
> >> on z/OS.
>
> >>
>
> >> In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.
>
> >>
>
> >> On z/OS, I expect I need to perform an OPEN against the volume using
>
> >> something like:
>
> >> //SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD
>
> >>
>
> >> Any pointers would be appreciated.
>
> >>
>
> >> My second question relates to 'authority'.
>
> >>
>
> >> On z/VSE, I have to tell the operating system that I am actually 'DSF'
>
> >> before it will allow me to issue these CCWs.
>
> >>
>
> >> Do I have to do something special on z/OS?
>
> >>
>
> >>
>
> >> Thanks,
>
> >>
>
> >> Tony Thigpen
>
> --
>
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and confidential.
> If the reader of the message is not the intended recipient or an authorized
> representative of the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please notify us immediately by
> e-mail and delete the message and any attachments from your system.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Tony Thigpen]

All,

No. I am not talking about scanning the volume nor reading the VTOC. I 
am not touching, in any way, the actual disk data. I am getting 
low-level info from the sub-system using CCW Commands:


x'27' PSSF - Perform Sub-System Function, functions 18/47, 18/0B
x'64' RDC - Read Device Characteristics
x'54' SSS - Sense Subsystem Status


Yep, not your common CCWs.

Tony Thigpen

Seymour J Metz wrote on 6/14/24 2:51 PM:

The OP was asking about scanning the entire volume, not just the VTOC.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of Mike Shaw 

Sent: Friday, June 14, 2024 1:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting dasd info

No. With the right combination of DYNALLOC, OPEN and RDJFCB you can open
the VTOC and execute a channel program that reads the entire VTOC without
any kind of SAF authorization. It can also be read with BSAM but that is a
little slower.

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd

On Fri, Jun 14, 2024, 1:17 PM Farley, Peter <
031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:


Doesn’t physical scan of VTOC/VVDS areas on DASD (or for that matter
directly issuing CCW’s to any DASD for any reason) also require at least
SAF authorization (if not also APF authorization) to allow access under
z/OS?

Peter

From: IBM Mainframe Discussion List  On Behalf
Of Matthew Stitt
Sent: Friday, June 14, 2024 1:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting dasd info


Take a look at file 527 on the CBT tape.  Program(s) DADSM and LISTICAT.
Both programs do a scan of the disk volumes and generate reports on VTOC,
VVDS, etc.



Matthew



On Fri, 14 Jun 2024 12:08:54 -0400, Mike Shaw 
wrote:




Tony,







You can run in problem program state and key and issue a UCBSCAN macro to



get a list of UCBs and UCB copies for that z/OS system. You can then run



that returned list and choose only the online DASD UCBs. For each of those



that you are interested in, issue an LSPACE SVC specifying the UCB

address.


That will get you a good picture of free space info for that volume, and



it's quick.







To go deeper and get a list of all data sets on the volume and/or a volume



map, you have to read the VTOC and process it. You can do that without



being APF authorized also, if the volume is allocated to your job step.







The CVAFTST macro will tell you whether or not a particular DASD volume

has


an indexed VTOC or not.







Mike Shaw



MVS/QuickRef Support Group



Chicago-Soft, Ltd.











On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:







All,







I have a z/VSE program that I want to start using with z/OS. The program



issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that



are either volume specific or subsystem specific. Not file specific.







My first question is in the area of getting access to a specific volume



on z/OS.







In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.







On z/OS, I expect I need to perform an OPEN against the volume using



something like:



//SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD







Any pointers would be appreciated.







My second question relates to 'authority'.







On z/VSE, I have to tell the operating system that I am actually 'DSF'



before it will allow me to issue these CCWs.







Do I have to do something special on z/OS?











Thanks,







Tony Thigpen


--

This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and confidential.
If the reader of the message is not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
dissemination of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
e-mail and delete the message and any attachments from your system.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Seymour J Metz]

Do those depend on specific bits in the file mask? If not, open any dataset for 
EXCP.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of 
Tony Thigpen 
Sent: Friday, June 14, 2024 3:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting dasd info

All,

No. I am not talking about scanning the volume nor reading the VTOC. I
am not touching, in any way, the actual disk data. I am getting
low-level info from the sub-system using CCW Commands:

x'27' PSSF - Perform Sub-System Function, functions 18/47, 18/0B
x'64' RDC - Read Device Characteristics
x'54' SSS - Sense Subsystem Status


Yep, not your common CCWs.

Tony Thigpen

Seymour J Metz wrote on 6/14/24 2:51 PM:
> The OP was asking about scanning the entire volume, not just the VTOC.
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> עַם יִשְׂרָאֵל חַי
> נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
>
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Mike Shaw 
> Sent: Friday, June 14, 2024 1:35 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Getting dasd info
>
> No. With the right combination of DYNALLOC, OPEN and RDJFCB you can open
> the VTOC and execute a channel program that reads the entire VTOC without
> any kind of SAF authorization. It can also be read with BSAM but that is a
> little slower.
>
> Mike Shaw
> MVS/QuickRef Support Group
> Chicago-Soft, Ltd
>
> On Fri, Jun 14, 2024, 1:17 PM Farley, Peter <
> 031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:
>
>> Doesn’t physical scan of VTOC/VVDS areas on DASD (or for that matter
>> directly issuing CCW’s to any DASD for any reason) also require at least
>> SAF authorization (if not also APF authorization) to allow access under
>> z/OS?
>>
>> Peter
>>
>> From: IBM Mainframe Discussion List  On Behalf
>> Of Matthew Stitt
>> Sent: Friday, June 14, 2024 1:00 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: Getting dasd info
>>
>>
>> Take a look at file 527 on the CBT tape.  Program(s) DADSM and LISTICAT.
>> Both programs do a scan of the disk volumes and generate reports on VTOC,
>> VVDS, etc.
>>
>>
>>
>> Matthew
>>
>>
>>
>> On Fri, 14 Jun 2024 12:08:54 -0400, Mike Shaw 
>> wrote:
>>
>>
>>
>>> Tony,
>>
>>>
>>
>>> You can run in problem program state and key and issue a UCBSCAN macro to
>>
>>> get a list of UCBs and UCB copies for that z/OS system. You can then run
>>
>>> that returned list and choose only the online DASD UCBs. For each of those
>>
>>> that you are interested in, issue an LSPACE SVC specifying the UCB
>> address.
>>
>>> That will get you a good picture of free space info for that volume, and
>>
>>> it's quick.
>>
>>>
>>
>>> To go deeper and get a list of all data sets on the volume and/or a volume
>>
>>> map, you have to read the VTOC and process it. You can do that without
>>
>>> being APF authorized also, if the volume is allocated to your job step.
>>
>>>
>>
>>> The CVAFTST macro will tell you whether or not a particular DASD volume
>> has
>>
>>> an indexed VTOC or not.
>>
>>>
>>
>>> Mike Shaw
>>
>>> MVS/QuickRef Support Group
>>
>>> Chicago-Soft, Ltd.
>>
>>>
>>
>>>
>>
>>> On Fri, Jun 14, 2024 at 11:20 AM Tony Thigpen  wrote:
>>
>>>
>>
 All,
>>

>>
 I have a z/VSE program that I want to start using with z/OS. The program
>>
 issues several CCWs to the DS8000, such as SNS, SSS, RCD, & PSSF that
>>
 are either volume specific or subsystem specific. Not file specific.
>>

>>
 My first question is in the area of getting access to a specific volume
>>
 on z/OS.
>>

>>
 In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.
>>

>>
 On z/OS, I expect I need to perform an OPEN against the volume using
>>
 something like:
>>
 //SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD
>>

>>
 Any pointers would be appreciated.
>>

>>
 My second question relates to 'authority'.
>>

>>
 On z/VSE, I have to tell the operating system that I am actually 'DSF'
>>
 before it will allow me to issue these CCWs.
>>

>>
 Do I have to do something special on z/OS?
>>

>>

>>
 Thanks,
>>

>>
 Tony Thigpen
>>
>> --
>>
>> This message and any attachments are intended only for the use of the
>> addressee and may contain information that is privileged and confidential.
>> If the reader of the message is not the intended recipient or an authorized
>> representative of the intended recipient, you are hereby notified that any
>> dissemination of this communication is strictly prohibited. If you have
>> received this communication in error, please notify us immediately by
>> e-mail and delete the message and any attachments from your system.
>>
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send emai

Re: As a long-time Rexx programmer (SDSF)

[Radoslaw Skorupka]

Friday, a little bit off-topic, but still about mainframes and SDSF

SDSF is great tool. I was enhanced significantly last years. I like it.
However I observe many users are simply *not aware* of many new features.
They obviously use panels, which are visible in main menu, but they miss 
many other tools.
I believe everything is documented, but it is rather rare that someone 
read whole documentation as a novel.


Q: is there any presentation or whitepaper describing "new and shining" 
things in SDSF?


Regarding SDSF and REXX - I miss simple examples. It is not only 
SDSF-related pain. I observe many z/OS users are looking for code 
samples via Google search and we find some bad or very bad ones, 
submitted on some forums.


My €0.02

Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 14.06.2024 o 20:20, Rob Scott pisze:

I must admit that I find nothing amiss with the quoted section.

  It describes the syntax requirements of the SDSF-specific ISFEXEC verb.

It does not get into any generic REXX techniques to provide the statement 
buffer to the verb as that is not required in this case.

  Contrast that with the documentation for ISFSLASH that does include required 
REXX techniques as it supports alternate input using stem variables.

The product documentation is written by information development team members, 
but based on input provided by the development team. In this case, that 
developer (not me) has decades of asm, plx and rexx experience and is fully 
aware of the nuances of the language.

The documentation will always be updated when required for the current (most 
recent) release.



Rob Scott
Rocket Software

Get Outlook for Android


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting dasd info

[Radoslaw Skorupka]

W dniu 14.06.2024 o 17:20, Tony Thigpen pisze:

All,

I have a z/VSE program that I want to start using with z/OS. The 
program issues several CCWs to the DS8000, such as SNS, SSS, RCD, & 
PSSF that are either volume specific or subsystem specific. Not file 
specific.


My first question is in the area of getting access to a specific 
volume on z/OS.


In z/VSE, I just do an ASSGN to the disk and issues the EXCPs.

On z/OS, I expect I need to perform an OPEN against the volume using 
something like:

//SOURCE DD UNIT=3390,VOL=SER=AVOLID,DISP=OLD

Any pointers would be appreciated.

My second question relates to 'authority'.

On z/VSE, I have to tell the operating system that I am actually 'DSF' 
before it will allow me to issue these CCWs.


Do I have to do something special on z/OS?



Out of curiosity: what kind of information do you want to get?
IMHO there are simpler ways & tools to get any information I could need.

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer

[Glenn Knickerbocker]

On Fri, 14 Jun 2024 11:51:23 -0400, Phil Smith III  wrote:
>"If the command contains special characters or blanks, enclose it in single 
>quotation marks."
>
>Might not be the best example, but it's clear from the doc that whoever wrote 
>it doesn't understand that unassigned Rexx variables return their literal 
>values.

Actually, it appears to be correct if unnecessary, and nothing to do with the 
REXX syntax.  I'm not all that familiar with SDSF, but after a little 
experiment I'm guessing the quotes either were required at some point in the 
past or are needed on some but not all commands.  I get the same results from 
these two commands to list my own jobs, with and without single quotes:

"ISFEXEC ST GSK*"
"ISFEXEC 'ST GSK*'"

If I put the command in double quotes instead:

'ISFEXEC "ST GSK*"'

I get an error telling me it's looking for quotes but not that kind:

ISF302E """ was seen in command position 9 where one of the following was 
expected: /, QUOTED-STRING, UNQUOTED-STRING. 

So I think this instruction really is about the actual command as evaluated, 
not the syntax of specifying it in REXX.

¬R

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer

[Farley, Peter]

I think we can blame JCL-based rules for that – I suspect that double-quote is 
NOT a valid substitute for apostrophe in those SDSF commands, as such 
substitution is also not valid in JCL.

After all, why would anyone use a “shift apostrophe” keystroke to get double 
quotes when simply typing the apostrophe will do?  Laziness rules.

Peter

From: IBM Mainframe Discussion List  On Behalf Of 
Glenn Knickerbocker
Sent: Friday, June 14, 2024 4:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: As a long-time Rexx programmer


On Fri, 14 Jun 2024 11:51:23 -0400, Phil Smith III  wrote:

>"If the command contains special characters or blanks, enclose it in single 
>quotation marks."

>

>Might not be the best example, but it's clear from the doc that whoever wrote 
>it doesn't understand that unassigned Rexx variables return their literal 
>values.



Actually, it appears to be correct if unnecessary, and nothing to do with the 
REXX syntax.  I'm not all that familiar with SDSF, but after a little 
experiment I'm guessing the quotes either were required at some point in the 
past or are needed on some but not all commands.  I get the same results from 
these two commands to list my own jobs, with and without single quotes:



"ISFEXEC ST GSK*"

"ISFEXEC 'ST GSK*'"



If I put the command in double quotes instead:



'ISFEXEC "ST GSK*"'



I get an error telling me it's looking for quotes but not that kind:



ISF302E """ was seen in command position 9 where one of the following was 
expected: /, QUOTED-STRING, UNQUOTED-STRING.



So I think this instruction really is about the actual command as evaluated, 
not the syntax of specifying it in REXX.



¬R

--



This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer (SDSF)

[Rob Scott]

For every z/OS release we also create a "What's new in SDSF" style presentation 
that we give at Share and GSE and then upload to the IBM Education GitHub. 
There is also an in-product help table of new functions for the release.

As for SDSF rexx examples, you can use the RGEN command that will generate 
sample rexx statements to navigate to where you currently are in the product OR 
use "RGEN X" to pick a sample from the supplied list of basic scenarios.

Rob Scott
Rocket Software.

Sent from Outlook for Android

From: IBM Mainframe Discussion List  on behalf of 
Radoslaw Skorupka <0471ebeac275-dmarc-requ...@listserv.ua.edu>
Sent: Friday, June 14, 2024 9:02:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: As a long-time Rexx programmer (SDSF)

EXTERNAL EMAIL




Friday, a little bit off-topic, but still about mainframes and SDSF

SDSF is great tool. I was enhanced significantly last years. I like it.
However I observe many users are simply *not aware* of many new features.
They obviously use panels, which are visible in main menu, but they miss
many other tools.
I believe everything is documented, but it is rather rare that someone
read whole documentation as a novel.

Q: is there any presentation or whitepaper describing "new and shining"
things in SDSF?

Regarding SDSF and REXX - I miss simple examples. It is not only
SDSF-related pain. I observe many z/OS users are looking for code
samples via Google search and we find some bad or very bad ones,
submitted on some forums.

My €0.02

Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 14.06.2024 o 20:20, Rob Scott pisze:
> I must admit that I find nothing amiss with the quoted section.
>
> It describes the syntax requirements of the SDSF-specific ISFEXEC verb.
>
> It does not get into any generic REXX techniques to provide the statement 
> buffer to the verb as that is not required in this case.
>
> Contrast that with the documentation for ISFSLASH that does include required 
> REXX techniques as it supports alternate input using stem variables.
>
> The product documentation is written by information development team members, 
> but based on input provided by the development team. In this case, that 
> developer (not me) has decades of asm, plx and rexx experience and is fully 
> aware of the nuances of the language.
>
> The documentation will always be updated when required for the current (most 
> recent) release.
>
>
>
> Rob Scott
> Rocket Software
>
> Get Outlook for Android>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ¦ 77 Fourth Avenue, Waltham MA 02451 ¦ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: DB2 V12 RSU2403

[Dave Beagle]

Depends on the holds. DOC holds are easily bypassed. Others not entirely 
bypass-able.(although most are) Some of them you might have to perform a bind 
to finish the installation. Here is a sample.
//WJJCAPCK JOB (3200,TBL1),'APCK DB2 MAINT',CLASS=8,MSGCLASS=Q,  
// NOTIFY=&SYSUID,REGION=6M
/*JOBPARM SYSAFF=BCWD
//*
//S1   EXEC PGM=GIMSMP,
// PARM='PROCESS=WAIT',
// DYNAMNBR=120
//*
//* NOTE:  THIS JCL CREATED BY THE COMMAND GENERATION DIALOGS.
//*
//*    SMP ZONE-RELATED FILES ARE DYNAMICALLY ALLOCATED,
//*    THIS INCLUDES THE SMPPTS, SMPLOG, AND SMPTLIB DATA SETS,
//*    IF APPLICABLE.
//*
//* SMP FILES
//*
//SMPCSI   DD DISP=SHR,DSN=SMPE.DB2V8R1.GLOBAL.CSI
//SMPOUT   DD SYSOUT=*
//SMPRPT   DD SYSOUT=*
//SMPLIST  DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//*
//*  UTILITY WORK DATA SETS IF REQUIRED FOR THE COMMAND
//*  FOLLOW HERE.
//*  INFORMATION FOR THE ALLOCATION OF THESE DATASETS IS
//*  SET USING OPTION 0 (SETTINGS) FROM THE SMP/E PRIMARY
//*  OPTION PANEL.
//*
//SYSUT1   DD UNIT=SYSDA,SPACE=(3120,(380,760))
//SYSUT2   DD UNIT=SYSDA,SPACE=(3120,(380,760))
//SYSUT3   DD UNIT=SYSDA,SPACE=(3120,(380,760))
//SYSUT4   DD UNIT=SYSDA,SPACE=(3120,(38,100))
//*
//*  SMP TEMPORARY WORK DATA SETS
//*
//SMPWRK1  DD UNIT=SYSDA,
//    SPACE=(3120,(364,380,500)),
//    DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK2  DD UNIT=SYSDA,
//    SPACE=(3120,(364,380,500)),
//    DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK3  DD UNIT=SYSDA,
//    SPACE=(3120,(364,380,500)),
//    DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK4  DD UNIT=SYSDA,
//    SPACE=(3120,(364,380,500)),
//    DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK6  DD UNIT=SYSDA,
//    SPACE=(3120,(364,380,500)),
//    DCB=(RECFM=FB,BLKSIZE=3120)
//*
//*
//SMPCNTL  DD *
  SET    BOUNDARY (DSN8TRG)
  .
  APPLY
 PTFS
 BYPASS   (
   HOLDSYSTEM
    (
  DOC
  DB2BIND
  IPL
  ACTION
  AO
  DEP
  DELETE
    )
  )
 JCLINREPORT
 CHECK
 EXCLUDE  (
   UK16725
   UK16766
   UK17549
   UK17614
   UK17616
   UK17619
   UK17786
   UK17972
   UK18140
   UK18173
   UK18509
   UK18859
   UK19013
   UK19209
   UK19249
   UK19337
   UK19345
   UK19528
   UK19578
   UK19603
   UK20093
   UK20531
   UK20550
   UK20557
   UK20696
   UK21117
  )
 GROUPEXTEND
 RETRY(YES)
    .

Dave

Sent from Yahoo Mail for iPhone


On Friday, June 14, 2024, 9:19 AM, Steve Beaver 
<050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:

Upfront - I am not a DB2 SYSPROG, SYSADM, or Programmer        

 

I have pulled in and applied DB2 V12 RSU2403.  That was the easy part.

 

There are 134 PTF's with HOLD ACTION and that is where  trouble is going to

Begin.

 

Does anyone have a Home Grown implementation document to help me get

Through these 134 PTF's with HOLD.

 

Thanks

 

Stev 

 

 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: DB2 V12 RSU2403

[Steely.Mark]

I usually just specify BYPASS(HOLDSYS)   - this why you don’t have to specify 
every HOLDSYS provided. 
Make sure you read what the HOLD action is. 

Thanks 

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Dave Beagle
Sent: Friday, June 14, 2024 5:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DB2 V12 RSU2403



CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? 
Were you expecting this email? If not, report it using the Report Phishing 
Button!

Depends on the holds. DOC holds are easily bypassed. Others not entirely 
bypass-able.(although most are) Some of them you might have to perform a bind 
to finish the installation. Here is a sample.
//WJJCAPCK JOB (3200,TBL1),'APCK DB2 MAINT',CLASS=8,MSGCLASS=Q,
// NOTIFY=&SYSUID,REGION=6M
/*JOBPARM SYSAFF=BCWD
//*
//S1   EXEC PGM=GIMSMP,
// PARM='PROCESS=WAIT',
// DYNAMNBR=120
//*
//* NOTE:  THIS JCL CREATED BY THE COMMAND GENERATION DIALOGS.
//*
//*SMP ZONE-RELATED FILES ARE DYNAMICALLY ALLOCATED,
//*THIS INCLUDES THE SMPPTS, SMPLOG, AND SMPTLIB DATA SETS,
//*IF APPLICABLE.
//*
//* SMP FILES
//*
//SMPCSI   DD DISP=SHR,DSN=SMPE.DB2V8R1.GLOBAL.CSI
//SMPOUT   DD SYSOUT=*
//SMPRPT   DD SYSOUT=*
//SMPLIST  DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//*
//*  UTILITY WORK DATA SETS IF REQUIRED FOR THE COMMAND
//*  FOLLOW HERE.
//*  INFORMATION FOR THE ALLOCATION OF THESE DATASETS IS
//*  SET USING OPTION 0 (SETTINGS) FROM THE SMP/E PRIMARY
//*  OPTION PANEL.
//*
//SYSUT1   DD UNIT=SYSDA,SPACE=(3120,(380,760))
//SYSUT2   DD UNIT=SYSDA,SPACE=(3120,(380,760))
//SYSUT3   DD UNIT=SYSDA,SPACE=(3120,(380,760))
//SYSUT4   DD UNIT=SYSDA,SPACE=(3120,(38,100))
//*
//*  SMP TEMPORARY WORK DATA SETS
//*
//SMPWRK1  DD UNIT=SYSDA,
//SPACE=(3120,(364,380,500)),
//DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK2  DD UNIT=SYSDA,
//SPACE=(3120,(364,380,500)),
//DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK3  DD UNIT=SYSDA,
//SPACE=(3120,(364,380,500)),
//DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK4  DD UNIT=SYSDA,
//SPACE=(3120,(364,380,500)),
//DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SMPWRK6  DD UNIT=SYSDA,
//SPACE=(3120,(364,380,500)),
//DCB=(RECFM=FB,BLKSIZE=3120)
//*
//*
//SMPCNTL  DD *
  SETBOUNDARY (DSN8TRG)
  .
  APPLY
 PTFS
 BYPASS   (
   HOLDSYSTEM
(
  DOC
  DB2BIND
  IPL
  ACTION
  AO
  DEP
  DELETE
)
  )
 JCLINREPORT
 CHECK
 EXCLUDE  (
   UK16725
   UK16766
   UK17549
   UK17614
   UK17616
   UK17619
   UK17786
   UK17972
   UK18140
   UK18173
   UK18509
   UK18859
   UK19013
   UK19209
   UK19249
   UK19337
   UK19345
   UK19528
   UK19578
   UK19603
   UK20093
   UK20531
   UK20550
   UK20557
   UK20696
   UK21117
  )
 GROUPEXTEND
 RETRY(YES)
.

Dave

Sent from Yahoo Mail for iPhone


On Friday, June 14, 2024, 9:19 AM, Steve Beaver 
<050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:

Upfront - I am not a DB2 SYSPROG, SYSADM, or Programmer



I have pulled in and applied DB2 V12 RSU2403.  That was the easy part.



There are 134 PTF's with HOLD ACTION and that is where  trouble is going to

Begin.



Does anyone have a Home Grown implementation document to help me get

Through these 134 PTF's with HOLD.



Thanks



Stev






--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: DB2 V12 RSU2403

[Steve Beaver]

The ones that scare me are the DB2BIND


Sent from my iPhone

No one said I could type with one thumb 

> On Jun 14, 2024, at 17:41, Steely.Mark  wrote:
> 
> I usually just specify BYPASS(HOLDSYS)   - this why you don’t have to 
> specify every HOLDSYS provided.
> Make sure you read what the HOLD action is.
> 
> Thanks
> 
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Dave Beagle
> Sent: Friday, June 14, 2024 5:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DB2 V12 RSU2403
> 
> 
> 
> CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? 
> Were you expecting this email? If not, report it using the Report Phishing 
> Button!
> 
> Depends on the holds. DOC holds are easily bypassed. Others not entirely 
> bypass-able.(although most are) Some of them you might have to perform a bind 
> to finish the installation. Here is a sample.
> //WJJCAPCK JOB (3200,TBL1),'APCK DB2 MAINT',CLASS=8,MSGCLASS=Q,
> // NOTIFY=&SYSUID,REGION=6M
> /*JOBPARM SYSAFF=BCWD
> //*
> //S1   EXEC PGM=GIMSMP,
> // PARM='PROCESS=WAIT',
> // DYNAMNBR=120
> //*
> //* NOTE:  THIS JCL CREATED BY THE COMMAND GENERATION DIALOGS.
> //*
> //*SMP ZONE-RELATED FILES ARE DYNAMICALLY ALLOCATED,
> //*THIS INCLUDES THE SMPPTS, SMPLOG, AND SMPTLIB DATA SETS,
> //*IF APPLICABLE.
> //*
> //* SMP FILES
> //*
> //SMPCSI   DD DISP=SHR,DSN=SMPE.DB2V8R1.GLOBAL.CSI
> //SMPOUT   DD SYSOUT=*
> //SMPRPT   DD SYSOUT=*
> //SMPLIST  DD SYSOUT=*
> //SYSPRINT DD SYSOUT=*
> //*
> //*  UTILITY WORK DATA SETS IF REQUIRED FOR THE COMMAND
> //*  FOLLOW HERE.
> //*  INFORMATION FOR THE ALLOCATION OF THESE DATASETS IS
> //*  SET USING OPTION 0 (SETTINGS) FROM THE SMP/E PRIMARY
> //*  OPTION PANEL.
> //*
> //SYSUT1   DD UNIT=SYSDA,SPACE=(3120,(380,760))
> //SYSUT2   DD UNIT=SYSDA,SPACE=(3120,(380,760))
> //SYSUT3   DD UNIT=SYSDA,SPACE=(3120,(380,760))
> //SYSUT4   DD UNIT=SYSDA,SPACE=(3120,(38,100))
> //*
> //*  SMP TEMPORARY WORK DATA SETS
> //*
> //SMPWRK1  DD UNIT=SYSDA,
> //SPACE=(3120,(364,380,500)),
> //DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
> //SMPWRK2  DD UNIT=SYSDA,
> //SPACE=(3120,(364,380,500)),
> //DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
> //SMPWRK3  DD UNIT=SYSDA,
> //SPACE=(3120,(364,380,500)),
> //DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
> //SMPWRK4  DD UNIT=SYSDA,
> //SPA

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: DB2 V12 RSU2403

[Dave Beagle]

Why? Generally you just need to rebind.


Sent from Yahoo Mail for iPhone


On Friday, June 14, 2024, 7:02 PM, Steve Beaver 
<050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:

The ones that scare me are the DB2BIND


Sent from my iPhone

No one said I could type with one thumb 

> On Jun 14, 2024, at 17:41, Steely.Mark  wrote:
> 
> I usually just specify BYPASS(HOLDSYS)  - this why you don’t have to specify 
> every HOLDSYS provided.
> Make sure you read what the HOLD action is.
> 
> Thanks
> 
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Dave Beagle
> Sent: Friday, June 14, 2024 5:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DB2 V12 RSU2403
> 
> 
> 
> CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? 
> Were you expecting this email? If not, report it using the Report Phishing 
> Button!
> 
> Depends on the holds. DOC holds are easily bypassed. Others not entirely 
> bypass-able.(although most are) Some of them you might have to perform a bind 
> to finish the installation. Here is a sample.
> //WJJCAPCK JOB (3200,TBL1),'APCK DB2 MAINT',CLASS=8,MSGCLASS=Q,
> //        NOTIFY=&SYSUID,REGION=6M
> /*JOBPARM SYSAFF=BCWD
> //*
> //S1      EXEC PGM=GIMSMP,
> //        PARM='PROCESS=WAIT',
> //        DYNAMNBR=120
> //*
> //* NOTE:      THIS JCL CREATED BY THE COMMAND GENERATION DIALOGS.
> //*
> //*            SMP ZONE-RELATED FILES ARE DYNAMICALLY ALLOCATED,
> //*            THIS INCLUDES THE SMPPTS, SMPLOG, AND SMPTLIB DATA SETS,
> //*            IF APPLICABLE.
> //*
> //* SMP FILES
> //*
> //SMPCSI  DD DISP=SHR,DSN=SMPE.DB2V8R1.GLOBAL.CSI
> //SMPOUT  DD SYSOUT=*
> //SMPRPT  DD SYSOUT=*
> //SMPLIST  DD SYSOUT=*
> //SYSPRINT DD SYSOUT=*
> //*
> //*      UTILITY WORK DATA SETS IF REQUIRED FOR THE COMMAND
> //*      FOLLOW HERE.
> //*      INFORMATION FOR THE ALLOCATION OF THESE DATASETS IS
> //*      SET USING OPTION 0 (SETTINGS) FROM THE SMP/E PRIMARY
> //*      OPTION PANEL.
> //*
> //SYSUT1  DD UNIT=SYSDA,SPACE=(3120,(380,760))
> //SYSUT2  DD UNIT=SYSDA,SPACE=(3120,(380,760))
> //SYSUT3  DD UNIT=SYSDA,SPACE=(3120,(380,760))
> //SYSUT4  DD UNIT=SYSDA,SPACE=(3120,(38,100))
> //*
> //*      SMP TEMPORARY WORK DATA SETS
> //*
> //SMPWRK1  DD UNIT=SYSDA,
> //            SPACE=(3120,(364,380,500)),
> //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
> //SMPWRK2  DD UNIT=SYSDA,
> //            SPACE=(3120,(364,380,500)),
> //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
> //SMPWRK3  DD UNIT=SYSDA,
> //            SPACE=(3120,(364,380,500)),
> //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
> //SMPWRK4  DD UNIT=SYSDA,
> //            SPA

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: As a long-time Rexx programmer

[Bob Bridges]

It used to, until I started doing a lot more coding in VBA, where double quotes 
are the rule for literal strings.  Now I find myself using double-quotes 
reflexively in REXX, too - very much to my dismay, because I'm with you, why 
use two fingers where one will do?

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* The conviction of the rich that the poor are happier is no more foolish than 
the conviction of the poor that the rich are.  -Mark Twain */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Farley, Peter
Sent: Friday, June 14, 2024 16:54

...why would anyone use a “shift apostrophe” keystroke to get double quotes 
when simply typing the apostrophe will do?  Laziness rules.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN