- Community Home
- >
- Storage
- >
- Legacy
- >
- Storage Software
- >
- How are people handling SSSU errors...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2010 02:16 PM - last edited on 02-23-2014 08:21 PM by Lisa198503
01-06-2010 02:16 PM - last edited on 02-23-2014 08:21 PM by Lisa198503
How are people handling SSSU errors...
As far as I can tell, there is minimal error trapping in sssu, at least on the openvms platform I'm using. If an error occurs in an sssu script, a text Error: message is displayed, and the script falls through to the next command. At the termination of SSSU, the $status variable contains 1, aka, success, whether or not any errors occurred.
How are people handling this? I already have a DCL script which logs in and runs scripts for me. I'm thinking of tricking this out to filter the sssu output and detect any "Error:
" strings. This is cheesy, but what else is there?
P.S. This thread has been moved from Disk Array to HP Storage System Scripting Utility (SSSU). -HP Forum Moderator