Printing it back to the spool is the way we've always done it. Here, they use a Print exit that massages the output class/writer/desk so we can't just do what we used to. Whole "customized" process. Yeah!! Thanks though.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
CMOD for z/OS Server / Re: ARSDOC get retrieval of report
August 15, 2024, 08:34:12 PM
I think i gave up on formatting the file on OMVS. Just spun it to a dataset on ispf. Removed the " -o agapp -d /u/home/w866451 " and it wrote the report out to STDOUT.
//W866451X JOB 0ZA103060401,'CMOD',MSGCLASS=X,MSGLEVEL=(1,1),
// CLASS=9,REGION=0M,NOTIFY=W866451,USER=W866451
//**** RESTART=REPT02
//************************************************************
//STEP01 EXEC PGM=BPXBATCH,REGION=0M
//ARSBIN DD PATH='/usr/lpp/ars/V10R5M0/bin'
//STDOUT DD DSN=&&TEMPRPT,DISP=(,PASS,DELETE),
// DCB=(DSORG=PS,RECFM=FBA,LRECL=132,BLKSIZE=0),
// UNIT=3390,SPACE=(TRK,(10,10),RLSE)
//STDERR DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//STDPARM DD *
SH /lpp/ars/V10R5M0/bin/arsdoc get
-h CMODT -v -f "Admin - Misc Reports"
-i "WHERE LOAD_DATE = '2024-08-13 19:39:37'"
-u xxxxxxx -p xxxxxxxx
//*****
//W866451X JOB 0ZA103060401,'CMOD',MSGCLASS=X,MSGLEVEL=(1,1),
// CLASS=9,REGION=0M,NOTIFY=W866451,USER=W866451
//**** RESTART=REPT02
//************************************************************
//STEP01 EXEC PGM=BPXBATCH,REGION=0M
//ARSBIN DD PATH='/usr/lpp/ars/V10R5M0/bin'
//STDOUT DD DSN=&&TEMPRPT,DISP=(,PASS,DELETE),
// DCB=(DSORG=PS,RECFM=FBA,LRECL=132,BLKSIZE=0),
// UNIT=3390,SPACE=(TRK,(10,10),RLSE)
//STDERR DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//STDPARM DD *
SH /lpp/ars/V10R5M0/bin/arsdoc get
-h CMODT -v -f "Admin - Misc Reports"
-i "WHERE LOAD_DATE = '2024-08-13 19:39:37'"
-u xxxxxxx -p xxxxxxxx
//*****
#3
CMOD for z/OS Server / ARSDOC get retrieval of report
August 15, 2024, 01:53:32 PM
I am trying to extract a z/OS loaded report by way of the arsdoc command. I am able to retrieve the report and store in a ZFS directory, but the format is unformatted. If I try to display it while in ISHELL and "View" I am prompted with a lrecl. My ultimate goal is to save as a DS to load for testing purposes. My first thought would have been to simply send a print out to a server printer, but the current Print exit is frustrating me.
000015 //STDPARM DD *
000016 SH /lpp/ars/V10R5M0/bin/arsdoc get
000017 -h CMODT -v -f "Admin - Misc Reports"
000018 -i "WHERE LOAD_DATE = '2024-08-13 19:39:37'"
000019 -o agapp -d /u/home/w866451
000020 -u xxxxxxx -p xxxxxxxxxx
000021 //*****
000015 //STDPARM DD *
000016 SH /lpp/ars/V10R5M0/bin/arsdoc get
000017 -h CMODT -v -f "Admin - Misc Reports"
000018 -i "WHERE LOAD_DATE = '2024-08-13 19:39:37'"
000019 -o agapp -d /u/home/w866451
000020 -u xxxxxxx -p xxxxxxxxxx
000021 //*****
#4
CMOD for z/OS Server / Re: Delegating Group User Admin Permissions(Pulling it back)
May 23, 2024, 03:06:44 PM
Seems from IBM that Group Owner field is the group DIRECTLY over the group. Not cascading.
#5
CMOD for z/OS Server / Delegating Group User Admin Permissions(Pulling it back)
May 15, 2024, 02:13:26 PM
I work for a large company that has, up until recently, decentralized user admin permissions for Groups/Folders. This is changing and not working as I'd expect. The GROUP OWNER field for GROUPS correlates to the owner of the group. These seemed to be set up for cascading levels, but I think it may only work ONE level up. When I've added a new User Admin to the Owning group, they CAN'T see 3 levels down. Is this working as designed? Truly a "flat" design?
#6
CMOD for z/OS Server / Re: How would multiple segments be opened?
January 31, 2024, 02:31:47 PM
Well, since one record segment was an anomaly, I thought I'd just close it. I think Justin mentioned that too.
arstblsp -a 1 -I CMODU -g "System Log" -t SL139
Worked just fine because the instance wasn't using it.
AG_NAME TABLE_NAME START_DATE START_DT POST_DT CLOSED_DT
------+---------+---------+---------+---------+---------+---------+---------+---------+---------+-----
System Log SL138 1705461323 2024-01-17-03.15.23.618709 2024-01-17 ----------
System Log SL139 1705461321 2024-01-17-03.15.21.378956 2024-01-17 2024-01-16
System Log SL137 1703798855 2023-12-28-21.27.35.117586 2023-12-28 2024-01-17
From the 10.5 manual. might be true if you wanted to close the ACTIVE segment, but not in this case :D
Important: The ARSTBLSP program can run without an active server. The server must be down to update
the System Log table
arstblsp -a 1 -I CMODU -g "System Log" -t SL139
Worked just fine because the instance wasn't using it.
AG_NAME TABLE_NAME START_DATE START_DT POST_DT CLOSED_DT
------+---------+---------+---------+---------+---------+---------+---------+---------+---------+-----
System Log SL138 1705461323 2024-01-17-03.15.23.618709 2024-01-17 ----------
System Log SL139 1705461321 2024-01-17-03.15.21.378956 2024-01-17 2024-01-16
System Log SL137 1703798855 2023-12-28-21.27.35.117586 2023-12-28 2024-01-17
From the 10.5 manual. might be true if you wanted to close the ACTIVE segment, but not in this case :D
Important: The ARSTBLSP program can run without an active server. The server must be down to update
the System Log table
#7
CMOD for z/OS Server / Re: How would multiple segments be opened?
January 30, 2024, 09:26:44 PM
Justin,
In both environments its a type 30 record.
one is from the zos loader
the other is from an odwek server.
In both environments its a type 30 record.
one is from the zos loader
the other is from an odwek server.
#8
CMOD for z/OS Server / Re: How would multiple segments be opened?
January 30, 2024, 09:13:45 PM
Seconds apart. Both the Prod instance and the Dev instance run on Parallel LPARS. (arssockd/loaders on two lpars for balancing). Possible that while loading at the exact same time, they both needed a new log. Only ONE record in the second segment.
the first one is PROD:
AG_NAME TABLE_NAME START_DATE START_TS CLOSED_DT INS_ROWS
---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+----
System Log SL297 1704756579 2024-01-08-23.29.39.030526 2024-01-23 10028002
System Log SL298 1705979559 2024-01-23-03.12.39.293026 ---------- 5101181
System Log SL299 1705979562 2024-01-23-03.12.42.171906 ---------- 1
Dev did the same thing:
AGID TABLE_NAME START_DATE START_DT POST_DT CLOSED_DT INS_ROWS
----+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+-------
30798 SL138 1705461323 2024-01-17-03.15.23.618709 2024-01-17 ---------- 1977724
30798 SL139 1705461321 2024-01-17-03.15.21.378956 2024-01-17 ---------- 1
30798 SL137 1703798855 2023-12-28-21.27.35.117586 2023-12-28 2024-01-17 2501758
the first one is PROD:
AG_NAME TABLE_NAME START_DATE START_TS CLOSED_DT INS_ROWS
---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+----
System Log SL297 1704756579 2024-01-08-23.29.39.030526 2024-01-23 10028002
System Log SL298 1705979559 2024-01-23-03.12.39.293026 ---------- 5101181
System Log SL299 1705979562 2024-01-23-03.12.42.171906 ---------- 1
Dev did the same thing:
AGID TABLE_NAME START_DATE START_DT POST_DT CLOSED_DT INS_ROWS
----+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+-------
30798 SL138 1705461323 2024-01-17-03.15.23.618709 2024-01-17 ---------- 1977724
30798 SL139 1705461321 2024-01-17-03.15.21.378956 2024-01-17 ---------- 1
30798 SL137 1703798855 2023-12-28-21.27.35.117586 2023-12-28 2024-01-17 2501758
#9
CMOD for z/OS Server / Re: How would multiple segments be opened?
January 29, 2024, 09:41:51 PM
Thanks. I thought of just closing the odd-ball segment. Might be wise.
#10
CMOD for z/OS Server / Re: DSNT408I SQLCODE = -804, ERROR
January 29, 2024, 02:34:00 PM
Funny, just saw one of these last week. Coming from an odwek server interface. Just a hickup. Assuming something was out of sync on the odwek server. Same Reason 07 too.
ARS0013E E476530 DB Error: {DB2 FOR OS/390}{ODBC DRIVER}{DSN12015}
DSNT408I SQLCODE = -804, ERROR: AN ERROR WAS FOUND IN THE APPLICATION
PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT, REASON 07
DSNT418I SQLSTATE = 07002 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXECP SQL PROCEDURE
DETECTING ERROR DSNT416I SQLERRD = -202 0 0
1 109840 0 SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'
FFFFFF36' X'00000000' X'00000000' X'FFFFFFFF' X'
0001AD10' X'00000000' SQL DIAGNOSTIC INFORMATION
ERRLOC=5:10:2 -- SQLSTATE=07002, SQLCODE=-804, File=arsdoc.c, Line=3442
DSNT408I SQLCODE = -804, ERROR: AN ERROR WAS FOUND IN THE APPLICATION
-------------------------------------------- V=IBM P=DB2 ERROR CODES R=V12 I=-804 D=M --
********************* Text Below Copyright (c) 2024, IBM *********************
-804
-804 AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE
SQL STATEMENT, REASON reason
Explanation
The call parameter list or the SQLDA is invalid.
o The call parameter list, which is created by the precompiler, might be
invalid if the application programmer has modified the output of the
precompiler, used a variable name beginning with 'SQL' in the
application program, or overwritten the call parameter list in some
other way.
o The SQLDA, which is created by the application program, has an invalid
data type or data length.
o The value of SQLDABC is not consistent with the value of SQLD.
The following is the list of reason codes:
01
Open issued for non-cursor.
02
07
SQLDA length is invalid.
ARS0013E E476530 DB Error: {DB2 FOR OS/390}{ODBC DRIVER}{DSN12015}
DSNT408I SQLCODE = -804, ERROR: AN ERROR WAS FOUND IN THE APPLICATION
PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT, REASON 07
DSNT418I SQLSTATE = 07002 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXECP SQL PROCEDURE
DETECTING ERROR DSNT416I SQLERRD = -202 0 0
1 109840 0 SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'
FFFFFF36' X'00000000' X'00000000' X'FFFFFFFF' X'
0001AD10' X'00000000' SQL DIAGNOSTIC INFORMATION
ERRLOC=5:10:2 -- SQLSTATE=07002, SQLCODE=-804, File=arsdoc.c, Line=3442
DSNT408I SQLCODE = -804, ERROR: AN ERROR WAS FOUND IN THE APPLICATION
-------------------------------------------- V=IBM P=DB2 ERROR CODES R=V12 I=-804 D=M --
********************* Text Below Copyright (c) 2024, IBM *********************
-804
-804 AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE
SQL STATEMENT, REASON reason
Explanation
The call parameter list or the SQLDA is invalid.
o The call parameter list, which is created by the precompiler, might be
invalid if the application programmer has modified the output of the
precompiler, used a variable name beginning with 'SQL' in the
application program, or overwritten the call parameter list in some
other way.
o The SQLDA, which is created by the application program, has an invalid
data type or data length.
o The value of SQLDABC is not consistent with the value of SQLD.
The following is the list of reason codes:
01
Open issued for non-cursor.
02
07
SQLDA length is invalid.
#11
CMOD for z/OS Server / Re: z/OS V3.1 Release Notes
January 29, 2024, 02:02:57 PM
Planning on this for 2024.
#12
CMOD for z/OS Server / How would multiple segments be opened?
January 29, 2024, 02:00:07 PM
I have question: We run CMOD on a sysplex with both ARSSOCKD running on 2 different LPARS as well as ARSLOAD running on 2 different LPARS. In looking at normal checking of the system we came across this anomaly. 2 different SEGMENTS open for the System Log. One record put into it. Odd that SL299 was opened without closing SL298. This installation stores the System log in CACHE. All Production AG data is in OAM.
This happened in both the Production Instance and the Dev instance. 2 different z/os datacenters. Prod on one, Dev on another. The system log only hangs around for 3-4 weeks (???) so it will probably go away on it's own. inquirying minds...
---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+--------
AG_NAME TABLE_NAME DATABASE_NAME START_DT CLOSED_DT LAST_UPDATE_DT INS_ROWS
---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+--------
System Log SL297 ARSDBAS8 2024-01-08 2024-01-23 2024-01-23-03.12.41.297427 10028002
System Log SL298 ARSDBAS8 2024-01-23 ---------- 2024-01-29-13.51.12.388742 4047185
System Log SL299 ARSDBAS8 2024-01-23 ---------- 2024-01-23-03.12.57.130152 1
DSNE610I NUMBER OF ROWS DISPLAYED IS 3
This happened in both the Production Instance and the Dev instance. 2 different z/os datacenters. Prod on one, Dev on another. The system log only hangs around for 3-4 weeks (???) so it will probably go away on it's own. inquirying minds...
---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+--------
AG_NAME TABLE_NAME DATABASE_NAME START_DT CLOSED_DT LAST_UPDATE_DT INS_ROWS
---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+--------
System Log SL297 ARSDBAS8 2024-01-08 2024-01-23 2024-01-23-03.12.41.297427 10028002
System Log SL298 ARSDBAS8 2024-01-23 ---------- 2024-01-29-13.51.12.388742 4047185
System Log SL299 ARSDBAS8 2024-01-23 ---------- 2024-01-23-03.12.57.130152 1
DSNE610I NUMBER OF ROWS DISPLAYED IS 3
#13
CMOD for z/OS Server / Re: ARSRPT hold back Load report
August 31, 2023, 02:16:13 PM
Agreed. Thought I'd ask. Thanks.
#14
CMOD for z/OS Server / ARSRPT hold back Load report
August 30, 2023, 07:32:11 PM
We run ARSRPT nightly. our server is at 10.5.0.4
As we are gathering data from the report it was discovered that occasionally ARSRPT omits LOAD data. Initially thinking excessive loads might contribute to this, but we have another day with over 300k and no issues.
Operating SSL Failed SSL
Client Version System Logins Logins Logins Failed
-------------- -------------- -------------- -------- -------- -------- -------
ADMIN GUI 10.5.0.2 Windows 10 0 0 0
ARSDOC 10.5.0.4 z/OS 21 0 0 0
ARSEXOAM 10.5.0.4 z/OS 1 0 0 0
ARSLOAD 10.5.0.4 z/OS 227064 0 0 0 <<<<==== 227064 loads on this day.
ARSMAINT 10.5.0.4 z/OS 2 0 0 0
CLIENT GUI 10.1.0.3 Windows 70 0 5 0
CLIENT GUI 10.1.0.4 Windows 727 0 19 0
CLIENT GUI 10.5.0.1 Windows 64 12 0 0 0
CLIENT GUI 10.5.0.2 Windows 266 0 13 0
CLIENT GUI 10.5.0.2 Windows 64 301 0 28 0
CLIENT GUI 9.5.0.8 Windows 615 0 50 0
ODF 10.5.0.4 z/OS 9 0 0 0
ODWEK JAVA API 10.1.0.0 Linux 281 0 0 0
ODWEK JAVA API 10.5.0.0 Linux 23099 0 87 0
ODWEK JAVA API 9.5.0.0 Linux 34762 0 2506 0
Looking down for the load data
-------------------------------------------------------------------------------
Load Activity
-------------------------------------------------------------------------------
No load activity for the given date
-------------------------------------------------------------------------------
We have another day will more loads and works fine:
Operating SSL Failed SSL
Client Version System Logins Logins Logins Failed
-------------- -------------- -------------- -------- -------- -------- -------
0 0 0 0
ADMIN GUI 10.5.0.2 Windows 8 0 7 0
ARSDOC 10.5.0.4 z/OS 36 0 0 0
ARSEXOAM 10.5.0.4 z/OS 1 0 0 0
ARSLOAD 10.5.0.4 z/OS 323075 0 0 0 <<=== 323075
ARSMAINT 10.5.0.4 z/OS 2 0 0 0
CLIENT GUI 10.1.0.3 Windows 199 0 6 0
CLIENT GUI 10.1.0.4 Windows 1057 0 56 0
CLIENT GUI 10.5.0.0 Windows 1 0 0 0
CLIENT GUI 10.5.0.1 Windows 64 18 0 0 0
CLIENT GUI 10.5.0.2 Windows 464 0 23 0
Just fine:
-------------------------------------------------------------------------------
Load Activity
-------------------------------------------------------------------------------
Loads by user - 1 user
Failed
Userid Loads Loads
---------------------------------------- -------- --------
ARSSERVR 322832 243
<TOTAL> 322832 243
Loads by application group/application - 4646 loads
Bytes
Application Group Application Loads Processe
------------------------------ ------------------------------ -------- --------
AC01 AC29901 1 2321886
AC02 AC29902 1 639730
AC03 AC29903 1 21413
AR99 AR099 1 713920
Is it possible the BYTE count is MAXING out? We load a lot of data every night.
Sample byte count by AG.
48,131,329
11,093,155
41,035,525
36,874,111
20,639,027
27,215,433
26,117,602
66,055,512
21,212,436
As we are gathering data from the report it was discovered that occasionally ARSRPT omits LOAD data. Initially thinking excessive loads might contribute to this, but we have another day with over 300k and no issues.
Operating SSL Failed SSL
Client Version System Logins Logins Logins Failed
-------------- -------------- -------------- -------- -------- -------- -------
ADMIN GUI 10.5.0.2 Windows 10 0 0 0
ARSDOC 10.5.0.4 z/OS 21 0 0 0
ARSEXOAM 10.5.0.4 z/OS 1 0 0 0
ARSLOAD 10.5.0.4 z/OS 227064 0 0 0 <<<<==== 227064 loads on this day.
ARSMAINT 10.5.0.4 z/OS 2 0 0 0
CLIENT GUI 10.1.0.3 Windows 70 0 5 0
CLIENT GUI 10.1.0.4 Windows 727 0 19 0
CLIENT GUI 10.5.0.1 Windows 64 12 0 0 0
CLIENT GUI 10.5.0.2 Windows 266 0 13 0
CLIENT GUI 10.5.0.2 Windows 64 301 0 28 0
CLIENT GUI 9.5.0.8 Windows 615 0 50 0
ODF 10.5.0.4 z/OS 9 0 0 0
ODWEK JAVA API 10.1.0.0 Linux 281 0 0 0
ODWEK JAVA API 10.5.0.0 Linux 23099 0 87 0
ODWEK JAVA API 9.5.0.0 Linux 34762 0 2506 0
Looking down for the load data
-------------------------------------------------------------------------------
Load Activity
-------------------------------------------------------------------------------
No load activity for the given date
-------------------------------------------------------------------------------
We have another day will more loads and works fine:
Operating SSL Failed SSL
Client Version System Logins Logins Logins Failed
-------------- -------------- -------------- -------- -------- -------- -------
0 0 0 0
ADMIN GUI 10.5.0.2 Windows 8 0 7 0
ARSDOC 10.5.0.4 z/OS 36 0 0 0
ARSEXOAM 10.5.0.4 z/OS 1 0 0 0
ARSLOAD 10.5.0.4 z/OS 323075 0 0 0 <<=== 323075
ARSMAINT 10.5.0.4 z/OS 2 0 0 0
CLIENT GUI 10.1.0.3 Windows 199 0 6 0
CLIENT GUI 10.1.0.4 Windows 1057 0 56 0
CLIENT GUI 10.5.0.0 Windows 1 0 0 0
CLIENT GUI 10.5.0.1 Windows 64 18 0 0 0
CLIENT GUI 10.5.0.2 Windows 464 0 23 0
Just fine:
-------------------------------------------------------------------------------
Load Activity
-------------------------------------------------------------------------------
Loads by user - 1 user
Failed
Userid Loads Loads
---------------------------------------- -------- --------
ARSSERVR 322832 243
<TOTAL> 322832 243
Loads by application group/application - 4646 loads
Bytes
Application Group Application Loads Processe
------------------------------ ------------------------------ -------- --------
AC01 AC29901 1 2321886
AC02 AC29902 1 639730
AC03 AC29903 1 21413
AR99 AR099 1 713920
Is it possible the BYTE count is MAXING out? We load a lot of data every night.
Sample byte count by AG.
48,131,329
11,093,155
41,035,525
36,874,111
20,639,027
27,215,433
26,117,602
66,055,512
21,212,436
Pages1