|
View previous topic :: View next topic
|
| Author |
Message |
parsesource
New User
Joined: 06 Feb 2006
Posts: 97
|
|
|
|
your program works great
i´ve added the following statement to a job-step
//STDERR DD PATH='/tmp/ASDFASDFASDFASDF.STDERR',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=SIRWXU
the program returns
DSInfo.DD = STDERR
DSInfo.DSN = ...PATH=.SPECIFIED...
so as an exercise to the reader, enhance the program to return unix paths too. i´ll try to get a working solution using bpxwdyn  |
|
| Back to top |
|
 |
bauer
New User
Joined: 03 Mar 2009
Posts: 28
Location: germany
|
|
|
|
| Quote: |
| so as an exercise to the reader, enhance the program to return unix paths too |
Just do it ! |
|
| Back to top |
|
|
PeD
Active User
Joined: 26 Nov 2005
Posts: 459
Location: Belgium
|
|
|
|
Aie, Eine Kleine Wolk
Bauer,
When I executed this program in a jobclass SWA=BELOW, it is fine.
When I ran the program in a jobclass SWA=ABOVE, the program did not give me back the correct SVAB.
As an example
Before starting the SAWREQ routine, display of SVAB is ‘00006F’x for the first file, “0000EF”x for the second, ‘00011F’x for the third, etc With this value the loop
| Code: |
| DO WHILE(SVAB > 65536); |
is never activated and the value of SVAB returned is
| Code: |
| SVAB = SVAB +1 +16 +l_QMAT |
which is decimal 2136813696 ( 111 + 1 + 16 + 2136813568 ) which seems to be not correct because they are junk characters and not the DSN, the DD name, etc.
| Code: |
| DSN = '5CE2E8000000B01D00007F0000007F5CE3A8000000B02900008F....'x |
I spent a part of the night on that. So maybe I need some rest  …..
An idea? Did I missed somethning?
Thanks
Pierre |
|
| Back to top |
|
|
bauer
New User
Joined: 03 Mar 2009
Posts: 28
Location: germany
|
|
|
|
Pierre,
the conversion of the three byte address token TIOEJFCB using routine SWAREQ seems to be wrong in case of 31 bit address. I have to check this.
bauer |
|
| Back to top |
|
|
|
|
