Library for job descriptions

What is the recommended location of user created job descriptions on the iSeries? Is there a nifty link or white paper on this kind of thing?
The system default is to place it in the current library of the job creating the job description. I normally place them in QUSRSYS, as this is normally in the system portion of the library list and all users have at least *USE authority to the library. I am not aware of any white papers or IBM Published standards on this subject.

==================================
MORE INFORMATION ON THIS TOPIC
==================================

The Best Web Links: tips, tutorials and more.

Ask your OS/400 questions -- or help out your peers by answering them -- in our live OS/400 discussion forums.

Ask the Experts yourself: Our OS/400 gurus are waiting to answer your questions.

Check out this Search400.com Featured Topic: 20 ways to ensure a smooth OS upgrade

Dig Deeper on Past Releases

Recovering your AS/400 security configuration You need to have your AS/400 security plan built into your disaster recovery process. Step 1: Know the security objects and settings, and how and where they are saved. These objects include private authorities, system values, and user profiles.

Read-only tip Times exist when you need to allow a user to sign on the system, but not let them modify data. In other words, they need to be a "look but don't touch" or have a "read-only" profile. Unfortunately, there is no system value or user profile attribute to configure this, so it will take a bit of work on your part to make this happen. Here are some suggested steps

Take the ugh out of upgrade: Prepare for V5R4 or other upgrades Anticipation mounts as the release of V5R4 nears. With upgrading comes a lot of uncertainty. What will IBM offer in this new release -- iSeries blade servers, more TCP/IP addresses, enhanced spool files? Well, we'll just have to patiently wait for the details, but in the meantime, we can bone up on iSeries upgrades in general. We can also review a few items that are rumored to be added or enhanced in the new release.

Security considerations for your library lists -- Part 2 If you reference the wrong object, you could process the wrong program or data -- possibly those that are malicious. You can avoid that by making sure your library lists are in order and the proper people have access to them. This week Rich Loeber details use of the product library and the current library.

Security considerations for your library lists -- Part 1 The library list on your i5-iSeries-AS/400 controls how OS/400 searches for objects when no specific library has been coded. Changes to the library list could easily be used to execute a rogue program or cause your processing to run against an incorrect set of data. Rich Loeber says controlling how your library lists are set up on your system can mean the difference between secure and insecure processing.

Controlling access to spool files Viewing spool files can be a helpful and convenient, but it is best to limit access to spool files for security reasons. This tip explains how to control spool file viewing.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

Meet all of our AS/400 experts

View all AS/400 questions and answers

Library for job descriptions

Dig Deeper on Past Releases

Related Q&A from John Brandt

Verifying a backup is complete

API to select a number at random

Date/time calculations on non-date fields in a stored procedure

Have a question for an expert?

Start the conversation

0 comments

Please create a username to comment.

-ADS BY GOOGLE

SearchDataCenter

Top 4 open source automation tools for admins

U.S. facility may have best data center PUE

Increase efficiency with data center temperature monitoring

Dig Deeper on Past Releases

Related Q&A from John Brandt

Have a question for an expert?

Start the conversation

0 comments

Register

Login

Forgot your password?

Your password has been sent to:

Please create a username to comment.