Name: Maria Senatore Strickland
Cell: 385.200.0122
Address: 415 W Twohig , 1D, San Angelo TX
Birthdate: 6-2-1960
Emergency contact
Dan Strickland. 512.666.4546
Danwstrickland@gmail.com
Lauren Strickland 325.277.2505
Jerry Strickland. 325.212.1099
Allergies
Morphine
Coceine
Codone
Demerol
Ibuprofen
Celebrex in ibuprofen family
Hydrocodone
Rosephen
Lipitor
Yellow dye 5
Diseases
Asthmatic
Copd
Diverticulitis
Des daughter
Hospital
Seton main - Austin
Shannon Hospital - San Angelo
Doctors
Viki Forlano - primary care - 325.481.2197
Oral Medicines
Family History
Father liver cancer
Mom diabetes
Maternal
Paternal grand father di
Past Surgeries
Deviate septum
4/2003 kidney biopsy
10/2003 port for chemo
12/2003 Stem cell transplant
2/2004 port removed
1/2014 Peritoneal catheter installed
5/2018 Peritoneal catheter removed
Monday, October 1, 2018
Friday, September 28, 2018
Thursday, September 13, 2018
Dan Emergency contact Info
Name: Dan Wayne Strickland
Cell: 512.666.4546
Address: 415 W Twohig , 1D, San Angelo TX
Birthdate: 2-15-1964
Emergency contact
Maria Strickland. 385.200.0122
Mariasstrickland@gmail.com
Lauren Strickland 325.277.2505
Jerry Strickland. 325.212.1099
Allergies
Tramadol
Cosopine
Ambien
Diseases
Multiple myelona
Kidney failure
On hemo dialysis
Easily goes in Afib
Hospital
Seton main - Austin
Shannon Hospital - San Angelo
MdAnderson - Houston
Doctors
Viki Forlano - primary care - 325.481.2197
William Rodriguez-kidney dr - 512.485.7872
Hans Lee - cancer dr - 713.792.3510
8323551432 cathy transplate nurse
Oral Medicines
Amlodipine Besylate 5mg 1x1
Metoprolol 50mg 1x2
Hydralazine 10mg if over 160/90
Levothyroxine .112mg 1x1
Sensipar 90mg 1x1
Auryxio 210mg 2×3
Bayer asprin 81mg
Dialyvite 800 with 15 zinc
Family History
Dad triple bypass surgery
Bladder cancer
Mom diabetes
Paternal grand father diabe
Past Surgeries
Deviate septum
4/2003 kidney biopsy
10/2003 port for chemo
12/2003 Stem cell transplant
2/2004 port removed
1/2014 Peritoneal catheter installed
5/2018 Peritoneal catheter removed
Cell: 512.666.4546
Address: 415 W Twohig , 1D, San Angelo TX
Birthdate: 2-15-1964
Emergency contact
Maria Strickland. 385.200.0122
Mariasstrickland@gmail.com
Lauren Strickland 325.277.2505
Jerry Strickland. 325.212.1099
Allergies
Tramadol
Cosopine
Ambien
Diseases
Multiple myelona
Kidney failure
On hemo dialysis
Easily goes in Afib
Hospital
Seton main - Austin
Shannon Hospital - San Angelo
MdAnderson - Houston
Doctors
Viki Forlano - primary care - 325.481.2197
William Rodriguez-kidney dr - 512.485.7872
Hans Lee - cancer dr - 713.792.3510
8323551432 cathy transplate nurse
Oral Medicines
Amlodipine Besylate 5mg 1x1
Metoprolol 50mg 1x2
Hydralazine 10mg if over 160/90
Levothyroxine .112mg 1x1
Sensipar 90mg 1x1
Auryxio 210mg 2×3
Bayer asprin 81mg
Dialyvite 800 with 15 zinc
Family History
Dad triple bypass surgery
Bladder cancer
Mom diabetes
Paternal grand father diabe
Past Surgeries
Deviate septum
4/2003 kidney biopsy
10/2003 port for chemo
12/2003 Stem cell transplant
2/2004 port removed
1/2014 Peritoneal catheter installed
5/2018 Peritoneal catheter removed
Friday, December 30, 2016
Microsoft 7.1 Requirements
http://support.sas.com/documentation/installcenter/en/ikmsofficeintsr/68008/PDF/default/sreq.pdf
Wednesday, December 14, 2016
Product Version - Determining your SAS® 9.4 release and which products are in each revision
http://support.sas.com/kb/50/493.html
SAS 9.4 includes several major releases and revisions that contain new software products and functionality.
A revision is a subset of a major release. An example of a revision is 13w26, which indicates that this revision was made available in the year 2013 during week 26. With this particular revision, SAS Institute introduced SAS 9.4 (TS1M0).
You need to know your release or revision for use in the SAS® Deployment Wizard and other SAS installation components. To determine which release or revision you have, open your SAS software order email and look at the section of the email entitled Information for Tech Support Site number. The site number contains a field named Product. The value in that field contains your revision level.
For example, if the value for Product is SAS® 9.4 (TS1M0), Rev. 940_13w26, then your revision level is 13w26.
Another way to determine your revision is to navigate to the directory \SAS Software Depot\install_doc\your order-number\ and open the soi.html file. The revision number is contained in this file. So, if the order number is 123456, open the soi.html file that resides in \SAS Software Depot\install_doc\123456\. For example: Z:\SAS Software Depot\install_doc\123456\soi.html.
This is similar to the following: Z:\SAS Software Depot\install_doc\123456\soi.html. In the soi.html file, the revision number appears as follows:
Product: SAS 9.4 TS1M0, Rev. 940_13w26
For more details about the soi.html file, see the "SAS Order Information" section in the SAS® 9.4 Guide to Software Updates.
SAS 9.4 includes several major releases and revisions that contain new software products and functionality.
A revision is a subset of a major release. An example of a revision is 13w26, which indicates that this revision was made available in the year 2013 during week 26. With this particular revision, SAS Institute introduced SAS 9.4 (TS1M0).
You need to know your release or revision for use in the SAS® Deployment Wizard and other SAS installation components. To determine which release or revision you have, open your SAS software order email and look at the section of the email entitled Information for Tech Support Site number. The site number contains a field named Product. The value in that field contains your revision level.
For example, if the value for Product is SAS® 9.4 (TS1M0), Rev. 940_13w26, then your revision level is 13w26.
Another way to determine your revision is to navigate to the directory \SAS Software Depot\install_doc\your order-number\ and open the soi.html file. The revision number is contained in this file. So, if the order number is 123456, open the soi.html file that resides in \SAS Software Depot\install_doc\123456\. For example: Z:\SAS Software Depot\install_doc\123456\soi.html.
This is similar to the following: Z:\SAS Software Depot\install_doc\123456\soi.html. In the soi.html file, the revision number appears as follows:
Product: SAS 9.4 TS1M0, Rev. 940_13w26
For more details about the soi.html file, see the "SAS Order Information" section in the SAS® 9.4 Guide to Software Updates.
SAS® 9.4 Revision Numbers and Associated Documentation
Table of Contents
SAS 9.4 (TS1M0) Revisions
SAS 9.4 (TS1M1) Revisions
- Revision 13w51
- Revision 14w04
- Revision 14w07
- Revision 14w11
- Revision 14w14
- Revision 14w19
- Revision 14w23
- Revision 14w25
- Revision 14w28
SAS 9.4 (TS1M2) Revisions
- Revision 14w32
- Revision 14w36
- Revision 14w41
- Revision 14w47
- Revision 15w04
- Revision 15w08
- Revision 15w12
- Revision 15w16
- Revision 15w17
- Revision 15w20
- Revision 15w25
SAS 9.4 (TS1M3) Revisions
- Revision 15w29
- Revision 15w33
- Revision 15w38
- Revision 15w42
- Revision 15w47
- Revision 16w04
- Revision 16w08
- Revision 16w13
- Revision 16w17
- Revision 16w22
- Revision 16w26
- Revision 16w30
- Revision 16w37
- Revision 16w43
SAS 9.4 (TS1M4) Revisions
Tuesday, December 13, 2016
Job - Hiring a SAS administrator? 12 questions to ask
http://blogs.sas.com/content/sgf/2013/04/10/hiring-a-sas-administrator-12-questions-to-ask/
I have been on both sides of the table during an interview to hire a SAS administrator. I’ve been hired as a SAS administrator, and I have hired SAS administrators. Today, I work with SAS customers to help them find the best software for their business needs. I get asked- a lot!- about how to find and to hire SAS administrators. How can you feel confident they know their stuff? Here is my personal list of interview questions.
Some of these questions can be answered from their resume, but if I’m doing a phone screen without the benefit of a resume, I’ll ask all of them. I have hired good SAS admins using this personal guidebook:
What SAS products and versions have you administered?
This question lets me know the breadth of their administration experience. Are they working with SAS metadata or not? The role of the SAS administrator became very important with SAS 9.
What operating system (OS) platforms have you used with SAS?
The more, the better! If I’m hiring for UNIX/LINUX and the candidate doesn’t have any experience outside of Windows, then I need to gauge how quickly they’ll pick it up. In this scenario, I’m going to usually prefer some that has UNIX/LINUX experience if they also have the SAS experience.
Which SAS products have you installed and configured?
I would also follow up this question with “Have you installed SAS Hot Fixes before”?
Do you have experience migrating content to new SAS versions?
Ask this question if necessary for your environment. If you are hiring to migrate from SAS Version 8 to SAS 9, ask if they have done that before.
How many SAS users have you supported? Business users? Power users?
This question gives me a general idea of how much work they had to do to support their users. If the company did not utilize metadata, what tasks did they perform in their administrator role? For business users, what is your role in pushing content out to them? For power users, how are you supporting your SAS developers?
Are you performing SAS product training for your SAS users?
If not, are they open to doing so? You have to decide if this is a requirement for your open position- not every administrator wants to be customer-facing or has the needed skills, even if the customers are internal. Some SAS administrators are more comfortable with server administration, while others prefer a more involved level of customer service to their users.
Are you doing any SAS development in you current role? Any experience with SAS development?
Have candidates designed any code, SAS Enterprise Guide projects, SAS Stored Processes or any other SAS content? From here, I recommend asking them to describe an example, such as "Walk me through the steps you took, from data management to analytics to reporting to sharing that information in the organization."
What level of support have you provided for your SAS users?
For example, did the candidate act as a first line of defense when users ran into problems? Do they work with their internal SAS user and SAS technical support where needed? Were they on call overnight, if that is a necessary part of the job requirements? How comfortable do they seem to be with troubleshooting a problem? Have candidates walk you through an example.
Describe the typical administrative tasks you perform each day.
The response to this question could be anything from kicking off jobs, restarting servers and backing up the environment to supporting users with coding questions. You should quickly get a sense for the type of daily tasks the candidate is used to performing.
Technically speaking….
I make sure I have candidates talk to me about the technical side of SAS administration, at least one story or explanation of how certain tasks are performed. Here are some questions to get them talking about their hands-on experience:
Do you have any other relevant experience?
Maybe the candidate has worked as a DBA. Maybe were an administrator for another software product. Maybe they’ve been a SAS user in another capacity. Get a sense for their technical savvy and their desire to learn something new. When I was very first hired to be a SAS administrator, I had never done it before- I had been a SAS programmer for a long time (more than 10 years), but had never been on the IT side of the house before. If I can learn it on the fly, I know there are others out there that can learn, too!
Don't forget to assess soft skills . . .
As I’m talking with the interviewee, I’m getting a sense of their technical ability as well as their interpersonal ability. Do they have the communication skills to explain something technically complex to a business user? Again, that might not be necessary for your environment. Add in questions that are relevant to your long-term vision of SAS and the roadmap to grow SAS. Will this person be a champion for SAS and for advanced analytics? Will this person help you go to the CIO and the CEO and explain why you need to hire more SAS users? Also, the most important of all, does this person have a quest to learn new things? If they do, they will help you troubleshoot even the most difficult of problems!
I hope these questions give you some good ideas of how to find a good SAS administrator. And if you’ve already found a good SAS administrator, go to them and say Thank You! They do so much for SAS and for your SAS users. For those of you that want to learn how to be a SAS administrator, hopefully this post gave you a good place to start. If you are looking to expand your knowledge of SAS administration, I recommend this training course: SAS Platform Administration: Fast Track.
I hope these questions give you some good ideas for finding a good SAS administrator. Please share some of your favorite interview questions!
I have been on both sides of the table during an interview to hire a SAS administrator. I’ve been hired as a SAS administrator, and I have hired SAS administrators. Today, I work with SAS customers to help them find the best software for their business needs. I get asked- a lot!- about how to find and to hire SAS administrators. How can you feel confident they know their stuff? Here is my personal list of interview questions.
Some of these questions can be answered from their resume, but if I’m doing a phone screen without the benefit of a resume, I’ll ask all of them. I have hired good SAS admins using this personal guidebook:
What SAS products and versions have you administered?
This question lets me know the breadth of their administration experience. Are they working with SAS metadata or not? The role of the SAS administrator became very important with SAS 9.
What operating system (OS) platforms have you used with SAS?
The more, the better! If I’m hiring for UNIX/LINUX and the candidate doesn’t have any experience outside of Windows, then I need to gauge how quickly they’ll pick it up. In this scenario, I’m going to usually prefer some that has UNIX/LINUX experience if they also have the SAS experience.
Which SAS products have you installed and configured?
I would also follow up this question with “Have you installed SAS Hot Fixes before”?
Do you have experience migrating content to new SAS versions?
Ask this question if necessary for your environment. If you are hiring to migrate from SAS Version 8 to SAS 9, ask if they have done that before.
How many SAS users have you supported? Business users? Power users?
This question gives me a general idea of how much work they had to do to support their users. If the company did not utilize metadata, what tasks did they perform in their administrator role? For business users, what is your role in pushing content out to them? For power users, how are you supporting your SAS developers?
Are you performing SAS product training for your SAS users?
If not, are they open to doing so? You have to decide if this is a requirement for your open position- not every administrator wants to be customer-facing or has the needed skills, even if the customers are internal. Some SAS administrators are more comfortable with server administration, while others prefer a more involved level of customer service to their users.
Are you doing any SAS development in you current role? Any experience with SAS development?
Have candidates designed any code, SAS Enterprise Guide projects, SAS Stored Processes or any other SAS content? From here, I recommend asking them to describe an example, such as "Walk me through the steps you took, from data management to analytics to reporting to sharing that information in the organization."
What level of support have you provided for your SAS users?
For example, did the candidate act as a first line of defense when users ran into problems? Do they work with their internal SAS user and SAS technical support where needed? Were they on call overnight, if that is a necessary part of the job requirements? How comfortable do they seem to be with troubleshooting a problem? Have candidates walk you through an example.
Describe the typical administrative tasks you perform each day.
The response to this question could be anything from kicking off jobs, restarting servers and backing up the environment to supporting users with coding questions. You should quickly get a sense for the type of daily tasks the candidate is used to performing.
Technically speaking….
I make sure I have candidates talk to me about the technical side of SAS administration, at least one story or explanation of how certain tasks are performed. Here are some questions to get them talking about their hands-on experience:
- “Describe to me how I would register a new table in SAS metadata”
- “Describe to me how I would add a new user and what permissions I can give that user”
- “What would you recommend I do for backing up my SAS environment?”
- “What does SAS do with authentication domains?”
- “How do you create a BASE engine library?”
- “Can you prevent a user from or ?”
- “What is an object spawner?”
Do you have any other relevant experience?
Maybe the candidate has worked as a DBA. Maybe were an administrator for another software product. Maybe they’ve been a SAS user in another capacity. Get a sense for their technical savvy and their desire to learn something new. When I was very first hired to be a SAS administrator, I had never done it before- I had been a SAS programmer for a long time (more than 10 years), but had never been on the IT side of the house before. If I can learn it on the fly, I know there are others out there that can learn, too!
Don't forget to assess soft skills . . .
As I’m talking with the interviewee, I’m getting a sense of their technical ability as well as their interpersonal ability. Do they have the communication skills to explain something technically complex to a business user? Again, that might not be necessary for your environment. Add in questions that are relevant to your long-term vision of SAS and the roadmap to grow SAS. Will this person be a champion for SAS and for advanced analytics? Will this person help you go to the CIO and the CEO and explain why you need to hire more SAS users? Also, the most important of all, does this person have a quest to learn new things? If they do, they will help you troubleshoot even the most difficult of problems!
I hope these questions give you some good ideas of how to find a good SAS administrator. And if you’ve already found a good SAS administrator, go to them and say Thank You! They do so much for SAS and for your SAS users. For those of you that want to learn how to be a SAS administrator, hopefully this post gave you a good place to start. If you are looking to expand your knowledge of SAS administration, I recommend this training course: SAS Platform Administration: Fast Track.
I hope these questions give you some good ideas for finding a good SAS administrator. Please share some of your favorite interview questions!
Wednesday, November 30, 2016
License - Update PC SAS license on multiple desktop computers
Update PC
SAS license on multiple desktop computers
- Update the PC SAS license on one of your desktop in the prescribed way. Usually this is using the renew.exe program. Once this is complete your one pc should be updated.
- Below are the three files that get updated
when a license file is applied. These are the files you'll need to copy from
the computer you updated today during our session to the other computers you
need to update.
C:\Program Files\SASHome\SASFoundation\9.4\core\sashelp\CORE.sas7bCATC:\Program Files\SASHome\SASFoundation\9.4\core\sasinst\setinit.sssC:\Program Files\SASHome\SASFoundation\9.4\core\sasinst\sid.txt
- Once these files are copied over to the other computers, you do not need to run the "renew sas software" tool at all. So, no further steps are required on the client machine to renew the license once the above files have been copied to each computer.
Thursday, August 28, 2014
Use - Starting and Stoping SAS servers in Unix
http://support.sas.com/documentation/cdl/en/bisag/64088/HTML/default/viewer.htm#a003280355.htm
During installation, the SAS Deployment Wizard creates a sas.servers script on each UNIX and z/OS server tier machine. You can perform the following tasks with this script:
![[cautionend]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_tTtmrXtwUBZxeTF3wejn-Gq9drxc2TMGfBsHXqx8e6Fiy_sOOLpiWfp_wKzCGzgf1hghvo-S2xG-n683XMwp7oE9CIfaGxIlqjHjflLLANtEcIILCFpOqGxFEUyQhuUYc725Ukvc5AgvE0F79Ugq2-EvyHnxcKo3ZbeFg=s0-d)
The script performs the preceding tasks for all instances of the following servers, spawners, and services that are installed on the machine:
To use the sas.servers script to start, stop, or restart all servers on a UNIX or z/OS machine or to display the status of all servers on the machine, follow these steps:
The generate_boot_scripts.sh script accesses each of the server-name.srv files to determine which servers and spawners are to be included in the sas.servers script. If a server's server-name.srv file contains the keyword ENABLE, then the server is included in the script. If the file contains the keyword DISABLE, then the server is excluded from the script.
In the initial configuration, all server-name.srv files contain the keyword ENABLE.
The server-name.srv files also contain the path to the server's startup script and the path to the server's log files.
On UNIX machines, you can choose to install the sas.servers script as a boot script so that the servers will start automatically when you start the machine. The comments in the sas.servers script contain installation instructions that are tailored to your operating environment.
Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers
| About the sas.servers Script |
During installation, the SAS Deployment Wizard creates a sas.servers script on each UNIX and z/OS server tier machine. You can perform the following tasks with this script:
- start, stop, or restart all of the SAS servers and spawners on the machine in the correct order by using a single command
- display the status of all the SAS servers and spawners on the machine by using a single command
The script performs the preceding tasks for all instances of the following servers, spawners, and services that are installed on the machine:
- SAS Metadata Server
- SAS object spawner
- SAS OLAP Server
- SAS/CONNECT spawner
- SAS/SHARE server
- SAS Table Server
- SAS Services Application (Remote Services)
- SAS Deployment Tester server
- CAUTION:
- You should not directly update the sas.servers script.If the script needs to be updated (for example, to add new servers or remove servers), then regenerate the script by using generate_boot_scripts.sh.
| Use the sas.servers Script to Start, Stop, or Restart All Servers or to Display the Status of Servers |
To use the sas.servers script to start, stop, or restart all servers on a UNIX or z/OS machine or to display the status of all servers on the machine, follow these steps:
- Log on as the SAS Installer user (for example, sas).
- Go to the directorySAS-configuration-directory/Lev1/.
- Type ./sas.servers followed by one of the following arguments:
- start
- starts the servers and spawners in the following order: SAS Metadata Server, SAS OLAP Server, SAS object spawner, SAS/SHARE server, SAS/CONNECT spawner, SAS Table Server, SAS Remote Services, SAS Deployment Tester server.
Note: The OLAP server, object spawner, SAS/SHARE server, SAS/CONNECT spawner, and table server require that the metadata server be running. If the metadata server is configured on a different host machine, make sure that the server is running before you use this script. - stop
- stops the servers and spawners in the following order: SAS Deployment Tester server, SAS Remote Services, SAS Table Server, SAS/CONNECT spawner, SAS/SHARE server, SAS object spawner, SAS OLAP Server, SAS Metadata Server.
Note:
- When you stop the metadata server, any dependent servers and spawners (whether they are on the same host machine or a different machine) will stop running.
- Before you stop an OLAP server, you should first stop the active sessions, as follows:
- In SAS Management Console, expand the Monitoring node and the SAS OLAP Server Monitornode.
- Right-click the name of the logical SAS OLAP Server, and select Connect.
- In the dialog box that appears, enter your user name and password and click OK.
- Right-click the name of each session that you want to close, and select Close Session.
- restart
- stops and then starts the servers and spawners in the following order: SAS Metadata Server, SAS OLAP Server, SAS object spawner, SAS/SHARE server, SAS/CONNECT spawner, SAS Table Server, SAS Remote Services.
- status
- displays the current status of the servers and spawners in the following format:
server-name server-instance(process-ID) is running|is stopped.
For example, the following messages mean that two instances of the SAS OLAP Server are configured on the machine. The first instance is running, and the second instance is stopped:
SAS OLAP Server 1 (pid 29529) is running SAS OLAP Server 2 (pid 29530) is stopped
| Using generate_boot_scripts.sh to Regenerate the sas.servers Script |
About generate_boot_scripts.sh
The generate_boot_scripts.sh script enables you to automatically regenerate the sas.servers script for a particular UNIX or z/OS host machine. This feature is useful in the following types of situations:- You have configured a new server or spawner on the machine. In this situation, the script generation process detects the new server or spawner and adds it to the sas.servers script.
- You have removed a server or spawner configuration from the machine. In this situation, the script generation process detects the absence of the server or spawner and removes it from the sas.servers script.
- You want to remove a server or spawner from the script so that you can operate it separately, or you want to add a server or spawner that you previously removed.
- You have changed the location of the server's log.
About the server-name.srv Files
On UNIX and z/OS systems, each server's configuration directory contains a file called server-name.srv. For example, the metadata server's configuration directory contains a file called MetadataServer.srv, and the workspace server's configuration directory contains a file called WorkspaceServer.srv.The generate_boot_scripts.sh script accesses each of the server-name.srv files to determine which servers and spawners are to be included in the sas.servers script. If a server's server-name.srv file contains the keyword ENABLE, then the server is included in the script. If the file contains the keyword DISABLE, then the server is excluded from the script.
In the initial configuration, all server-name.srv files contain the keyword ENABLE.
The server-name.srv files also contain the path to the server's startup script and the path to the server's log files.
Regenerate the sas.servers Script
To regenerate the sas.servers script, follow these steps:- Log on as the SAS Installer user (for example, sas).
- If you want to remove a server or spawner from the script, or if you want to add a server or spawner that you previously removed, follow these steps:
- Navigate to the server's configuration directory and open the file server-name.srv in an editor.
For example, if you want to remove the SAS/SHARE server from the script, you would go to SAS-configuration-directory/Lev1/ShareServer and open the file ShareServer.srv. - Locate the line that contains the keyword ENABLE or DISABLE. If you want to exclude the server from the sas.servers script, change the keyword to ENABLE. If you want to include the server in the sas.servers script, change the keyword to DISABLE. Save the file.
- Navigate to the server's configuration directory and open the file server-name.srv in an editor.
- Go to the directorySAS-configuration-directory/Lev1/.
- Enter the following command:./generate_boot_scripts.sh
A new sas.servers script is created to reflect the servers that are currently configured on the machine. If any of the server-name.srv files contain the keyword DISABLE, the following message appears:
<number-of-disabled-servers> SAS servers were explicitly disabled in their .srv files
| Install sas.servers as a Boot Script |
On UNIX machines, you can choose to install the sas.servers script as a boot script so that the servers will start automatically when you start the machine. The comments in the sas.servers script contain installation instructions that are tailored to your operating environment.
 |
Monday, August 25, 2014
Configure - Changing SASAdm password
Here is a step by step process for change passwords on SAS EBI
1. ADD *SAS (this is the Local or Domain account you install SAS with) to the AdminUser.txt file.
2. Restart the Metadata server
3. In you SASHome directory start the SAS Deployement Manager.
4. Complete the prompts correctly. and Once this is all complete get out SAS DM.
5. Remove *SAS from the AdminUser.txt file
6. Restart the SAS metadata server.
1. ADD *SAS (this is the Local or Domain account you install SAS with) to the AdminUser.txt file.
2. Restart the Metadata server
3. In you SASHome directory start the SAS Deployement Manager.
4. Complete the prompts correctly. and Once this is all complete get out SAS DM.
5. Remove *SAS from the AdminUser.txt file
6. Restart the SAS metadata server.
Wednesday, July 9, 2014
Boot time of your computer
From the run prompt. Type CMD.
In the CMD window type systeminfo.
A listing will give the boot time as well as system information.
In the CMD window type systeminfo.
A listing will give the boot time as well as system information.
Firewall timeout issue
There are many times that you start to run a Enterprise Guide flow process and it takes a large amount of time to complete the processing of the flow. During that time your Enterprise Guide project losses connection and you have to start over. This has been a big issue for our state agency.
So let me tell you what is not the problem. Enterprise Guide is not the problem, so there is no setting or configuration that can be changed to correct this problem. The changes that need to be made are on the firewall side of this equation. When Enterprise Guide opens a connection it opens a connection to the metadata server port as well as a connection to the workspace server port. That workspace server port is continually be accessed so the timeout does not occur there. The connection to the metadata server is where the problem lies. Once the metadata verify your credentials it is not accessed again. When the firewall sees that the connection to the metadata server has not be accessed within the time that it has been set (most of the time 1 hour) it breaks that connection and that cause your flow process to not be able to be completed. Have your firewall timeout increase to more than the time it take for you to complete your flow process and the process will complete without problems.
So let me tell you what is not the problem. Enterprise Guide is not the problem, so there is no setting or configuration that can be changed to correct this problem. The changes that need to be made are on the firewall side of this equation. When Enterprise Guide opens a connection it opens a connection to the metadata server port as well as a connection to the workspace server port. That workspace server port is continually be accessed so the timeout does not occur there. The connection to the metadata server is where the problem lies. Once the metadata verify your credentials it is not accessed again. When the firewall sees that the connection to the metadata server has not be accessed within the time that it has been set (most of the time 1 hour) it breaks that connection and that cause your flow process to not be able to be completed. Have your firewall timeout increase to more than the time it take for you to complete your flow process and the process will complete without problems.
Thursday, June 26, 2014
Subscribe to:
Posts (Atom)