× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Becky,

I was not aware of this, SAVSYS includes a SAVSECDTA.
I agree with Pete, it is probably one or more user profiles.

DSPOBJD OBJ(QSYS/*ALL) OBJTYPE(*USRPRF)

Profiles taking more than 999,999 could be your culprits. Someone once granted themselves authority to every object on the system, their profile was huge.
Also, if you have many private authorities, other culprits.

Opt Object Type Attribute Size Text
U8MIS *USRPRF 135168 Sharred account
WSC *USRPRF 6393856

Save Security Data - Help

The Save Security Data (SAVSECDTA) command saves all security
information without requiring a system in a restricted state. The
SAVSECDTA command saves the same security information that is saved
when a Save System (SAVSYS) command is run including the following:

o User Profiles

o Authorization Lists

o Authority Holders

Information saved with the SAVSYS or SAVSECDTA command can be
restored using the Restore User Profiles (RSTUSRPRF) and Restore
Authority (RSTAUT) commands.

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello - ML
Sent: Monday, April 22, 2013 7:40 PM
To: Midrange Systems Technical Discussion
Subject: RE: Long SAVSYS

Becky,

I bet the culprit is authorities. Try running a SAVSECDTA (which you can run when the system is up and everyone is using the system. If this takes a long time, you know what the problem is. I bet it isn't the OS part of the save that has increased, in most cases it is the security data.

pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bakutis, Becky
Sent: Monday, April 22, 2013 4:23 PM
To: Midrange Systems Technical Discussion
Subject: RE: Long SAVSYS

In the past my savsys was consistently 90 minutes which is still too long. The time never changed after an IPL until now. The savsys ran from 2:19 until 3:48:

4/21/13 2:19:15 Begin processing for control group SAVSYSLTO4 type *BKU.
4/21/13 2:19:16 Devices TAPMLB09 will be used for control group SAVSYSLTO
4/21/13 2:19:17 Interactive user QSECOFR with job DSP01 exempted from aut
4/21/13 2:19:17 Interactive usage check indicated no user jobs active on
4/21/13 2:19:19 Change to media controls successful.
4/21/13 2:19:20 Change to media controls successful.
4/21/13 2:19:20 Starting SAVSYS to devices TAPMLB09.
4/21/13 3:48:45 Save System (SAVSYS) command has completed processing.
4/21/13 3:48:47 SAVSYS is complete.

I am going to check to see if I have a tape drive issue next. Does anyone else save the IBM items in the ifs? In the past I would save *LNK, but found that took way too long so I contacted IBM and they suggested this:

Display Link List (DSPLNKLBRM)

Type choices, press Enter.

List . . . . . . . . . . . . . . > QIBMLINK Character value
Objects:
Name . . . . . . . . . . . . . > '/QIBM/ProdData'
Include or omit . . . . . . . *INCLUDE *INCLUDE, *OMIT

Name . . . . . . . . . . . . . > '/QOpenSys/QIBM/ProdData'
Include or omit . . . . . . . *INCLUDE *INCLUDE, *OMIT
Directory subtree . . . . . . . *ALL *ALL, *DIR, *NONE, *OBJ
Text . . . . . . . . . . . . . . > 'All IBM directories'

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Monday, April 22, 2013 12:37 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Long SAVSYS

Becky,

Your first save after an IPL will be longer than normal, per IBM document.
Once every object is touched 1st time, save will be quicker.

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, April 22, 2013 3:32 PM
To: Midrange Systems Technical Discussion
Subject: Re: Long SAVSYS

Becky,

If you look at the DSPLOGBRM type(*bku) can you tell what steps ran the longest?

From my system:
Date sent Time sent Message
4/06/13 17:43:14 Begin processing for control group DTFULL type *BKU.
4/06/13 17:43:17 Devices TAPGRT01 will be used for control group DTFULL ty
4/06/13 17:43:17 Interactive users are allowed to stay active.
4/06/13 17:44:05 Change to media controls successful.
4/06/13 17:44:05 Change to media controls successful.
4/06/13 17:44:05 Starting SAVSYS to devices TAPGRT01.
4/06/13 17:50:25 Save System (SAVSYS) command has completed processing.

4/06/13 17:50:26 SAVSYS is complete.
4/06/13 17:50:39 Starting *IBM backup, type *FULL.
4/06/13 17:50:39 Change to media controls successful.
4/06/13 17:50:39 Change to media controls successful.
4/06/13 17:50:39 Starting save of library *IBM to devices TAPGRT01.
4/06/13 17:50:41 1 blocks processed for sequence 43, volume BR0205, on dev
4/06/13 17:50:44 27 blocks processed for sequence 44, volume BR0205, on de
4/06/13 17:50:54 94 objects saved from library QAPTL.
...
4/06/13 17:57:20 1 objects saved from library Q1ABRMSF01.
4/06/13 17:57:20 84 libraries saved at 04/06/13 17:50:39.
4/06/13 17:57:23 Backup *IBM, type *FULL complete.
4/06/13 17:57:23 Starting *ALLUSR backup, type *FULL.
4/06/13 17:57:23 Change to media controls successful.
4/06/13 17:57:24 Change to media controls successful.
4/06/13 17:57:24 Starting save of library *ALLUSR to devices TAPGRT01.

4/06/13 17:57:25 1 blocks processed for sequence 128, volume BR0205, on de
4/06/13 17:57:30 173 blocks processed for sequence 129, volume BR0205, on
4/06/13 17:57:35 276 objects saved from library QSYS2.
...
4/06/13 18:07:42 27 libraries saved at 04/06/13 17:57:24.
4/06/13 18:07:49 Change to media controls successful.
4/06/13 18:07:49 Change to media controls successful.
4/06/13 18:07:49 Starting save of library QUSRBRM to devices TAPGRT01.

4/06/13 18:09:18 22116 blocks processed for sequence 156, volume BR0205, o
4/06/13 18:09:25 246 objects saved from library QUSRBRM.
4/06/13 18:09:26 Backup *ALLUSR, type *FULL complete.
4/06/13 18:09:26 Change to media controls successful.
4/06/13 18:09:26 Change to media controls successful.
4/06/13 18:09:33 16 document library objects saved.
4/06/13 18:09:34 Change to media controls successful.
4/06/13 18:09:34 Change to media controls successful.
4/06/13 18:09:34 Starting save of list *LINK to devices TAPGRT01.
4/07/13 0:39:18 Volume BR0205 on device TAPGRT01 is density *ULTRIUM3.

4/07/13 0:39:20 1738661 blocks processed for sequence 158, volume
BR0205,
4/07/13 0:39:20 End of volume BR0205 reached on device TAPGRT01.
4/07/13 0:39:20 End of volume detected for file QSYSTAP in QSYS.
4/07/13 0:39:21 1871854 blocks processed for sequence 158, volume
BR0217,
4/07/13 0:39:21 End of volume BR0217 reached on device TAPGRT01.
4/07/13 0:39:21 End of volume detected for file QSYSTAP in QSYS.
4/07/13 0:39:21 2057199 blocks processed for sequence 158, volume
BR0212,
4/07/13 0:39:21 End of volume BR0212 reached on device TAPGRT01.
4/07/13 0:39:21 End of volume BR0212 reached on device TAPGRT01.
4/07/13 0:39:21 End of volume detected for file QSYSTAP in QSYS.
4/07/13 0:39:21 1241526 blocks processed for sequence 158, volume
BR0073,
4/07/13 0:39:21 1766630 objects saved.
4/07/13 0:48:33 Save of list *LINK complete.
4/07/13 0:48:35 Starting save of media information at level *LIB to
devic
4/07/13 0:48:40 Change to media controls successful.
4/07/13 0:48:40 Change to media controls successful.
4/07/13 0:48:55 427 blocks processed for sequence 159, volume BR0073,
on
4/07/13 0:49:05 15 objects saved from library QUSRBRM.
4/07/13 0:49:06 Save of BRM media information at level *LIB complete.

4/07/13 0:50:52 Control group DTFULL type *BKU processing is complete.


Sometimes that *LINK can be significant! Of course, when your *link includes nine Domino partitions...


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Bakutis, Becky" <BBakutis@xxxxxxxxxxxxxxxxxxxx>
To: "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>,
Date: 04/22/2013 02:32 PM
Subject: Long SAVSYS
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I IPL'ed and applied PTFs this weekend. I ran a SAVSYS plus other IBM items and it took 1 hour 50 minutes. Is there anything I can check to clean up? I am using an LTO 4. Other systems take less than 1 hour for this process, but this is the largest system. Here is the BRMS control
group:


Backup List Parallel Private
Seq Items Type Type Authorities Encrypt
10 *EXIT
20 *SAVSYS
30 *IBM *NO
40 QIBMLINK *LNK *DEFAULT *NO *NO
50 *EXIT

Display Link List (DSPLNKLBRM)

Type choices, press Enter.

List . . . . . . . . . . . . . . > QIBMLINK Character value
Objects:
Name . . . . . . . . . . . . . > '/QIBM/ProdData'
Include or omit . . . . . . . *INCLUDE *INCLUDE, *OMIT

Name . . . . . . . . . . . . . > '/QOpenSys/QIBM/ProdData'
Include or omit . . . . . . . *INCLUDE *INCLUDE, *OMIT
Directory subtree . . . . . . . *ALL *ALL, *DIR, *NONE, *OBJ
Text . . . . . . . . . . . . . . > 'All IBM directories'




Becky Bakutis
Systems Engineer
Republic Services

480.627.2760 (w)
bbakutis@xxxxxxxxxxxxxxxxxxxx

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.