Show Posts

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.


Messages - Darrell Bryant

Pages: 1 [2] 3 4 5 6
16
Application group query information is captured in the system log only if it has been turned in the Application Group, the default is that query activity is not logged. The message numbers are 65 (before the query is run) and 226 (after the query is run, contains the number of hits returned).
Document retrieval information is logged by default, but can be turned off. The message number is 66.
All loading activity is logged. The message number is 87. This can also be determined from the System Load facility.

If this is a small customer with only one System Log table (SL2) then you can use SQL to analyze the activity. If they have multiple System Log tables then I think is easier to perform the analysis by searching the System Log using the client.

Using the client you could pick a date range, specify an In search for Msg Num with value 65 66 87, and a Like search for Message with value %<name of AG>%.

I don't know enough SQL to only return one row per AG per activity (query, retrieve, load), which is what you want.

As for leaving the Document Activity Tracking turned on in the AG permanently, I would say it depends on the existing workload on the system. Having the current information might be valuable to some customers, justifying the overhead.

17
MP Server / Re: Successful Load Fails to Unload
« on: June 22, 2022, 04:12:43 AM »
When specifying the load id you can always specify the dates as 0.  The application id is also optional.

For example, you could use either of these formats:

13031-46-0-57FAA-0-0-0
or
13031-46-0-57FAA-0-0

See the documentation of arsadmin parameters here:
https://www.ibm.com/docs/en/cmofm/10.5.0?topic=arsadmin-parameters

18
At v7.5 the Add Report (ADDRPTOND) command now supports the ability to convert an input spooled file from SCS or AFPDS to PDF before indexing and loading into Content Manager OnDemand. Subsequent retrievals of the archived data are displayed and printed as PDF.

This support uses the PDF Indexer, and requires the full Adobe Acrobat product on the workstation of any administrator that is using the graphical indexer to create parameters for the PDF Indexer.

The new support requires IBM Transform Services for i licensed program product (5770-TS1).

More details will be in the 2Q2022 OnDemand Newsletter.

19
Other / Re: ARSDOC Delete - Can a file be 'Undeleted'?
« on: May 27, 2022, 09:36:49 AM »
The document is not actually deleted, just the indexes.  You could try to recover that one index from a backup of the AG index table.  Or you could try to recreate the indexes based on the offsets and sizes from the other documents in that specific load.

20
z/OS Server / Re: Security Exit for Document Permissions
« on: May 10, 2022, 08:51:50 AM »
Have you looked into Query Restrictions?  Query Restrictions are used to limit the documents a user can access.  They are set in the Application Group > Permissions.

21
Other / Re: Query Restrictions - How to filter based on current date
« on: March 25, 2022, 11:53:43 AM »
You don't mention which database you are using. Db2 supports 'CURRENT DATE'.  Quoting from the z/OS Db2 documentation:
"The CURRENT DATE special register specifies a date that is based on a reading of the time-of-day clock when the SQL statement is executed at the current server."
and this
"Specifying CURRENT_DATE is equivalent to specifying CURRENT DATE"

If this is my data, where JLDATE has a data type of Date:
JOBNAME     JLDATE   
DSP01       05/24/15
ONDUNI1     01/10/17
QP0ZSPWT    02/03/17
NC4057D0    03/25/22
QP0ZSPWT    06/30/22


When I run this SQL:
SELECT JOBNAME, JLDATE FROM ARCHIVE.WGSM1 WHERE JLDATE <= CURRENT_DATE ORDER BY JLDATE

I receive this result:
JOBNAME     JLDATE 
DSP01       05/24/15
ONDUNI1     01/10/17
QP0ZSPWT    02/03/17
NC4057D0    03/25/22


Or to flip that around, this SQL statement:
SELECT JOBNAME, JLDATE FROM ONDENU.WGSM1 WHERE CURRENT_DATE <= JLDATE

Produces this result:
JOBNAME     JLDATE 
NC4057D0    03/25/22
QP0ZSPWT    06/30/22


I tested this with a query restriction, you have to enter the query restriction using the keyboard, and not using the "BuildSQL" function.  I used this query restriction:

JLDATE <= CURRENT_DATE

And in the client the same two rows listed above are returned.

22
Report Indexing / Re: Bad Character in data file
« on: March 15, 2022, 07:45:56 AM »
For our IBM i customers, we tell them the following about indexing and UTF-8 databases, and this probably applies to all platforms:

  • Some characters will use more than one byte when stored in a UTF-8 field
  • Latin lowercase and uppercase characters [a-z] [A-Z] and Arabic numerals [0-9] use only one byte
  • Accented characters might use two bytes
  • For languages such as Greek, Russian, & Arabic, we recommend that you create application group string fields with double the length you would use if the instance did not support UTF-8
  • For other languages, if your index values contain accented characters, you will need to make the fields longer
    For example, ẞ requires two bytes
  • DBCS characters might use two or three bytes
  • When setting up new reports you might need to increase the field length determined by the graphical indexer to accommodate accented characters

23
Tips and Tricks / Re: Document size on disk i AFP format
« on: February 02, 2022, 06:29:29 AM »
Once the System Load facility is created / activated it is used by all Application Groups. If your System Load entries start in 2017, then yes, that is when someone in your organization ran the steps to create the facility.
Note that the System Load facility does not get updated if data is unloaded.

24
General / Re: arsdoc get
« on: February 01, 2022, 02:18:39 PM »
The arsdoc get command created generic indexer files.  On the arsload command, should the indexer be overridden from the 390 indexer to the generic indexer since the data is already indexed?  The -X G parameter would do that.

25
Tips and Tricks / Re: Document size on disk i AFP format
« on: January 31, 2022, 06:38:20 AM »
The System Load facility was first available about 2010 as a part of the 8.4.1.x server version. On Multi-platforms the creation of the System Load facility was optional and required customer action.
The first System Load table is SA2, there was never an SA1 (just as the first System Log table was SL2).

26
MP Server / Re: Determine the active segment table being used
« on: December 20, 2021, 05:45:54 AM »
Running arstblsp -a 3 without the AG name lists all AGs in the instance and the open table for each. For example:

arstblsp -a 3 -h QUSROND
ARS1304I Table still open for loading:  ApplGroup(Statements) Agid(243679) Table(CBCL1)           
ARS1304I Table still open for loading:  ApplGroup(REPORT1) Agid(243676) Table(BBCL1)             
ARS1304I Table still open for loading:  ApplGroup(ARSR1MST) Agid(225773) Table(DKKK1)             
ARS1304I Table still open for loading:  ApplGroup(TEGDB260) Agid(215817) Table(XTZJ1)   \
ARS1304I Table still open for loading:  ApplGroup(JOBLOG9LO) Agid(28417) Table(TVV1)
ARS1304I Table still open for loading:  ApplGroup(System Load) Agid(5011) Table(SA2)
ARS1304I Table still open for loading:  ApplGroup(System Log) Agid(5001) Table(SL2)
etc

If you specify the AG name then only that AG is listed. For example:

arstblsp -a 3 -g JOBLOG9LO -h QUSROND
ARS1304I Table still open for loading:  ApplGroup(JOBLOG9LO) Agid(28417) Table(TVV1)

27
If the new folder field maps to an existing application group field, the value in the AG field will be displayed in the folder.
If the new folder field maps to a new application group field, for existing rows the new AG field will be populated with default values when the field is added. The default values depend on the field type. That is documented somewhere, but I could not put my hands on it.

28
Other / Re: System Log data query
« on: November 18, 2021, 06:48:34 AM »
The ANNOT field is not used to determine the Yes/No status of the View field in the System Log folder.
If the DOC_NAME field is not blank, then View is set to Yes in the hit list of the System Log.
In SQL you can see that by using this statement:
SELECT MSG_NUM, DOC_NAME, "USERID" FROM QUSROND.SL2 WHERE "USERID" =
'DBRYANT' AND MSG_NUM IN (34, 35, 36) AND DOC_NAME != ' ' 

MSG_NUM   DOC_NAME     USERID 
     34   41FAA        DBRYANT
     34   45FAA        DBRYANT
     34   75FAA        DBRYANT
     35   75FAA        DBRYANT   

29
Windows Client / Re: Duplicating users
« on: August 26, 2021, 08:42:11 AM »
The problem with arsxml, as I see it, is that the new LDAP users need to have the same permissions as the old RACF users. I tested exporting users using arsxml, and the only permissions exported are to the user itself, not the Application Group and Folder permissions.  Without the Application Group and Folder permissions, adding users using arsxml does not appear to meet the requirements.

30
Windows Client / Re: Duplicating users
« on: August 23, 2021, 10:53:00 AM »
You might give each person adding users a range of UIDs to specify. UIDs do not have to be consecutive. Give one person 1000 thru 1399 and another 1400 thru 1799, for example.
 

Pages: 1 [2] 3 4 5 6