Kbase 19398: How to avoid error code 100 start in Progress/400 Data Dictionary
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/31/2008 |
|
Status: Verified
GOAL:
How to avoid error code 100 start in Progress/400 Data Dictionary
FACT(s) (Environment):
IBM AS/400 (RISC)
Progress/400 DataServer
FIX:
When a DBA tries to switch to Modify Schema mode in the PROGRESS/400 Data Dictionary and the job attribute ALWMLTTHD of the PROSERVER is set to *YES, he will experience the following error:
A DBA COMMAND ERROR HAS OCCURED CONTACT PROGRESS SOFTWARE WITH THE
FOLLOWING ERROR CODE 100 START.
When the error is generated due to the value of this job attribute the way to prevent is to set ALWMLTTHD to *NO (the default value) in the job description of the user profile which starts the broker (PROTCPBRK).
These are some possible ways to do this:
- Changing the job description:
If you do not know the job description you should take a look at the user profile that is used to start the proserver using DSPUSRPRF, once you find it you can change it with the following OS400 command:
CHGJOBD JOBD(Job description) ALWMLTTHD(*NO)
- Another way to avoid it is changing the user profile's job description to the default QDFTJOBD on the QGPL using the following OS400 command:
CHGUSRPRF USRPRF(userprf) JOBD(library/jobd)
- You could also create a job description using the OS400 command:
CRTJOBD
In order to verify the value of the job attribute:
- On the PROSERVER or PROTCPBRK
Go to Work with Active Jobs (WRKACTJOB)
On the job (PROTCPBRK) type option 5 (5=Work with) and press enter
Then select:
2. Display job definition attributes
The definition of this job attribute would look like:
Allow multiple threads . . . . . . . . . . . . . : *Yes
- On the job description
You can also check the job attribute value directly in the job description with the following OS400 command:
DSPJOBD JOBD(library/JOBD)
1. The job attribute "Allow Multiple Threads (ALWMLTTHD)" specifies whether or not the job can run with multiple threads.
2. The job attribute is not allowed to be changed once a job starts.
3. The job attribute applies to autostart jobs, prestart jobs, batch jobs submitted from job schedule entries and jobs started using the Submit Job (SBMJOB) and Batch Job (BCHJOB) commands.
4. The job attribute is ignored when starting all other types of jobs.
5. The job attribute should be set to *YES only in job descriptions used exclusively with functions that support multiple threads.