Support Forums > z/OS Server

How would multiple segments be opened?

<< < (2/2)

scott.walsh:
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 

scott.walsh:
Justin,
   In both environments its a type 30 record.

one is from the zos loader
the other is from an odwek server.

scott.walsh:
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

Navigation

[0] Message Index

[*] Previous page