| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| DMS Systems Support Q and A for DMS Systems |

![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #2 (permalink) | ||||||||
| Junior Member ![]()
Location: Chlt-NC Rep Power: 6 ![]() | Patch Auto Apply My suggestion. Here is how we have AUTOPRSU set. >table autoprsu TABLE: AUTOPRSU >lis all TOP KEY MTWTFSS ---------------- FILEAUD YYYYYYY PREMON YYYYYYY AUTOAPP NNNNNNN POSTMON YYYYYYY STATAUD YYYYYYY BOTTOM As you see, AUTOAPP (Auto Apply) is set to No. This gives us a chance to review the patches before they are blindly applied. Once reviewed, set AutoApp to Y for the day you want the patches applied. *Remember Table AUTOOPTS controls the time the above activities take place. To make it easy to know what is downloaded and new use a volume to store newly downloaded patches. Once they are apllied you can copy to store file, then copy over to your SLM drives. Look at table PADNDEV. This table defines the location that patches downloaded via the turbolink are located. The first entry in the table is the first location patches will download to. We typically like to use a disk volume not on the SLM's. For example, our first entry in PADNDEV is D000PATCH. Once patches are downloaded, list the volume (LIV D000PATCH ALL). Then go into PRSM and do a DISADM patchname. This way you will know what patches are being applied to your system and what they are for. Next set the day you wish to have the patches applied to Y in AUTOAPP and you are good to go. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member ![]()
Rep Power: 5 ![]() | We have our auto apply turned off also, there was a patch applied that caused a issue in our system. I go through prsm once a month a apply patches. Here is how you find patches that need validation, and then the patches which are validated. If all your patches have been vailidated then you will need to manually apply them if you have the autoapply turned off. CI: >prsm PRSM: Welcome to PRSM - Post Release Software Manager. Type Q PRSMCI for a list of available commands, or Type HELP for a list of available help topics. >select nvstat PRSUID ST DESTID -------------------- -- ---------------------- No entry found. PRSUID ST DESTID -------------------- -- ---------------------- No entry found. PRSUID ST DESTID -------------------- -- ---------------------- No entry found. PRSUID ST DESTID -------------------- -- ---------------------- No entry found. >select vastat PRSUID ST DESTID -------------------- -- ---------------------- SRS49B9F VA CM KZY52B9M VA CM KZY22B9M VA CM KZY05B9C VA CM KZY56B9E VA CM KZY46B9E VA CM KZY36B9E VA CM KZY51B9E VA CM KZY45B9E VA CM KZY21B9E VA CM NFT86B9E VA CM KZY18B9D VA CM WBA64B9D VA CM KZY16B9D VA CM JLC99B9D VA CM TUN44B9C VA CM AHM53B9C VA CM KZY69B9E VA CM KZY68B9E VA CM CFZ39B9E VA CM NOV31B9E VA CM CFZ37B9E VA CM WBA63B9D VA CM KZY14B9C VA CM RTA02B9C VA CM NBT25B9A VA CM PRSUID ST DESTID -------------------- -- ---------------------- NBT25I9A VA EIU 101 NBT25I9A VA EIU 102 PRSUID ST DESTID -------------------- -- ---------------------- XXU56X7A VA RCC2 3 0 XXU56X7A VA RCC2 3 1 XXU56X7A VA RCC2 4 0 XXU56X7A VA RCC2 4 1 PRSUID ST DESTID -------------------- -- ---------------------- No entry found. >>apply XXU56X7A | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Adding a feature globally to SL100 | dmsman | DMS Systems | 12 | 08-24-2007 07:01 AM |
| Meridian SL100 | dixiedogger | Meridian Systems | 2 | 10-27-2004 08:15 PM |
| SL100 | EricP | Meridian Systems | 1 | 09-08-2004 11:34 PM |
| SL100 Procomm terminal | Tonka56 | Technology Chat | 2 | 06-22-2003 07:49 PM |
| Attn. SL100 guru's | renegade | Technology Chat | 1 | 03-27-2003 09:20 PM |