In this user guide, we are going to find out some of the possible causes that adding a working autorun subsystem might cause, and after that, we will provide some possible fixes that you can try to fix the problem.
Recommended
g.To attach an autorun task to a subsystem, you need two things: a task description that describes the task parameters and the enhancement environment in which the task will run; and any good boot job record to add to your target subsystem. For an auto-start job, the job description contains all the execution position parameters required to complete the job.
If I knew that the boot tasks belong to me in the IBM i partitions, I would display either using the DSPSBSD command to display your boot tasks for each subsystem, or even using the API. Fortunately, the latest tech updates include Db2, a crosshair for all of us that gives me the details I need.
Before giving examples of using the new view, I really want to show you how you can get the same information using the DSPSBSD command so you can evaluate the data for both.
If I want to see which startup projects are in the QCTL subsystem, I would use the following command:
Recommended
Is your PC running slow? Do you have problems starting up Windows? Don't despair! Fortect is the solution for you. This powerful and easy-to-use tool will diagnose and repair your PC, increasing system performance, optimizing memory, and improving security in the process. So don't wait - download Fortect today!
Pressing the Enter key will display your current menu as follows:
As you can imagine, it takes some time to create the autorun information in the subsystem. If I had originally planned to experience all autostarts after running multiple subsystems, I would repeat this for each one. That’s when styling becomes a pain!
I can now use the SQL view: AUTOSTART_JOB_INFO that I findIn the QSYS2 library. There are only five columns in this view. I will not list these views here, since the column names summarize what they contain.
Here I can get a feel for displaying all columns from the normal view, but usually only from the QCTL subsystem description in the local QSYS library.
It was easy. What about each bit of autorun tasks for all subsystems:
I did not bother to specify the names of the columns to sort, I just entered a number if it matches the position in the view where the column is located.
Results are probably below, only part of the activity was returned:
It was that easy, for example, compared to what you would have to do with the DSPSBSD command:
- Find all objects describing the subsystem.
- use the DSPSBSD command to get each one because I can’t be sure which autorun roles have and which don’t.
- Select multiple options from the menu.
- Write down the names or whatever I need from the two autorun tasks.
- Go to step 2.
This takes a long time. Using All View saves me the time I can spend getting ready for more productive things.
For more information on SQL View autostart_job_info visit the IBM website here.
This information was written for IBM i 7.4 TR 2 and 7.3 TR 8.
Subsystem Fur Autostart Job Hinzufugen
Autostart Taaksubsysteem Toevoegen
Ajouter Un Sous Systeme De Travail A Demarrage Automatique
Lagg Till Undersystem For Autostart Jobb
Agregar Subsistema De Trabajo De Inicio Automatico
Dobavit Podsistemu Avtozapuska Zadanij
Dodaj Podsystem Zadan Autostartu
자동 시작 작업 하위 시스템 추가
Adicionar Subsistema De Trabalho De Inicializacao Automatica
Aggiungi Il Sottosistema Del Lavoro Di Avvio Automatico
